4 ms·
I mean - a good job will ramp you up. But generally, you want to start small, on tasks that will expose you to the ins and outs of the codebase, and you want a
by mock-possum 4y ago
I mean - a good job will ramp you up.
But generally, you want to start small, on tasks that will expose you to the ins and outs of the codebase, and you want another more experienced dev to be ‘on call’ to help you out when you get stuck for the first few sprints. That’s the kind of support you wanna look for.
- jholman 4y ago> I mean - a good job will ramp you up. I wonder if I will ever work at a good job. That would be pleasant.
- ResearchCode 4y agoGenerally the good jobs don't have "sprints".
- Jeremy1026 4y agoWhy not? Having a clear, defined, roadmap and the ability to plan out work is a fantastic thing to have.
- ResearchCode 4y agoUnnecessary overhead and micromanagement. You don't need "sprints" for any of that.
- mock-possum 4y agoSprints are pretty common in my experience in software dev, and I’ve never had a problem with them… what makes you say that?
- ResearchCode 4y agoThey're the open office plan of project management. Tech workers have open offices, other professionals don't. I think we're just treated more poorly in some regards. Sprints tend to create lots of of tech debt and they're used for micromanagement. You want to work in 3-6 month projects, not 2 week arbitrary deadlines. Not sure your average PhD at Microsoft Research or Jane Street would put up with them. Linux Kernel developers don't use them. Mathematicians don't story point conjectures. But creating CRUD apps for a non-tech enterprise, you might have lots of "sprints" but no software is delivered reliably or high in quality.