tetonraven
tetonraven on Hacker News
Most important is to ignore a candidate's proven ability to deliver real solutions and instead focus on contrived tests that bear no resemblance to the actual work they'd be doing.
Maybe some detail would help. I have interviewed and hired people, been a dev team lead and manager. I would consider a such a candidate enough to at least get them on the phone and see where it goes. Just wondering if I'm alone here (especially because I have a personal bias in this case).
Is there any common resource that people use for judging reputation of these programs? For what it's worth, the context for my question is for one in Boulder called RefactorU. I've been a web developer for (well, a while) but my wife wants to get into the field and this program looks pretty good to me.
Any detail on why not? A categorical or conditional no?
Posted by
tetonraven on Tuesday January 19, 2016 @03:01PM
from the self-post dept.
Would you hire somebody who's gone through a 10 week MEAN bootcamp as a junior developer, assuming they also had a running site they'd built, with source on GitHub?
Oh. And definitely bringing that domain knowledge (medical) is an advantage to getting into your first programming gig.
Yes! I never got a CS degree (or any degree, actually) and I've been professional programmer for more than 20 years. I've also been in the position of interviewing/hiring developers and never paid any attention to degrees. I think it's more about what you can do (or have done) and the way you approach development; a curiosity for continuous learning and improvement is way better than a degree. That said, I'm not too current on getting into the field but there is a lot of demand right now and if you can use personal learning (or a bootcamp sort of thing) plus demonstrated work to get your foot in the door, you're on your way. Good luck!
First off, each person shouldn't have "their" stories. The stories in the sprint backlog should be owned by and worked by the entire team. Second, not everything needs to be a story or a task in the backlog; agile isn't about tracking every activity. Everybody will have things outside of planned stories (meetings, time off, whatever). If you feel the need to get detailed about it and plan at the hours level, assume a baseline "development hours per day" (6 is a common one) and adjust for planned time off. If your team is not able to get in the development hours you're expecting, there's something else wrong; such as a "manager" asking you to do TPS reports, outside the scope of the project your team is actually working on. Anyway, velocity at the point level is a better measure of a team's ability to take on a certain amount of work in an upcoming sprint, because it inherently accounts for distractions. However you do it, don't get too caught up on detailed accounting and planning of hours; that's not how agile works. And definitely don't create "stories" for things that aren't actual user stories.
The goal is to have a potentially shippable product increment at the end of each sprint. You don't have to release it to production; but it should certainly be made available for review/feedback by stakeholders and either customers or a representative of the customer. There's no reason you can't use all agile principles (or, say, Scrum as-is) on long release cycles. You will have to break that pattern of months of development without testing and a final "stabilization" phase.
In other news... Studies show that eating hamburgers is always the healthiest choice for any person on any diet. Read more at McDonalds.com.
Another thing. Don't create "technical stories". They are not user stories and that undermines Scrum in a variety of ways. One important consideration, too, is this... Even if it's completely horrid code, unless there's a bug against it, it's presumably working in production and it's hard to show value in fixing it. When bad code hinders progress on new functionality, though, there's clear value in changing it and it can be done with appropriate visibility on the changed areas.
The first step, of course, is to stop accumulating it. As for dealing with what's already there... The right approach is to chip away at it incrementally, cleaning up related code with any new work you take on; among other benefits, that reduces chances of introducing undetected bugs by refactoring. You can adjust story point estimates accordingly or just accept a reduced velocity. The key is for the team and organization to be on the same page in regards to the value of this.
I would suggest committing to just try it. If you give an honest try at putting quality and testing center-stage in your development, I think you'll start to see the value and eventually get hooked on it. Start with unit tests and grow from there. There was a time when I thought unit tests were a "nice-to-have-sometimes" sort of thing. Now, I fully embrace TDD and writing tests (first) is an integral part of my development. This has grown into a comprehensive test strategy with automation at various levels. Maybe it sounds simplistic, but just start with forcing yourselves to write unit tests for all new code and see where it takes you. Be sure you are writing good tests, though, otherwise you'll reinforce a non-test approach by seeing poor outcomes; there are a lot of sources on how to write good unit tests.