4 ms·

Developers are still constrained by process, and it's their fault. In every single company I have worked, the process always took priority. It's made even wors

Developers are still constrained by process, and it's their fault. In every single company I have worked, the process always took priority. It's made even worse where you have ISO 9001 compliance where every god damn thing in the company is locked into a "process." Process over people, period. Coporo-managers can't get it out of their head. When all you have ever done is "the process" it looks perfectly sane. To teams that can produce a POC and basically get to market on their own domain knowledge, it looks ridiculous. Making developers wait for requirements instead of inventing them on the fly is incredibly slow and smothers nearly all innovation. Why risk making your product look like your convoluted communication and political structures? The entire point of agile was lost on the influx of bodies to the industry. Form a "skunk works" team and shield them. Make a big show of how their success came despite having zero fucking process. Jira is for maintenance.

kayodelycaon 2y ago
> Developers are still constrained by process, and it's their fault. How is it my fault? I don’t get to make the decisions and I can’t just change jobs if management doesn’t listen.
- datavirtue 2y ago
  That's why it's your fault, because you won't make decisions. You feel like there are rules and guardrails constraining you and bringing order to society but it is not so. If you envision the reality and live it, then it will manifest. Some people thinks this means being forceful and demanding. Just the opposite. Then again, I doubt the company has a reward structure in place that even makes the mental energy worth expending. If you aren't on the way up, then you are on the way out.
toast0 2y ago
> In every single company I have worked, the process always took priority. If process (or freedom from process) is important to you, you need to make it a priority when you're interviewing. May depend on what industry you work in, of course, some industries don't have any cowboys. That said, I like my cowboy jobs with a little bit of process. What's deployed in production should be reflected in source control, but I'm not a stickler for which comes first. A change notification should be posted before production is changed, but if you have separate push and load steps, you can push before you notify (if pushing takes a while, it's good pipelining to use the push time to compose your change notice). Changelogs usually shouldn't be 'bugfixes' or 'latest', but 'fixing' is appropriate for a close in time followup. That's process, even if an ISO compliance officer would lose their mind.

kayodelycaon 2y ago

> Developers are still constrained by process, and it's their fault. How is it my fault? I don’t get to make the decisions and I can’t just change jobs if management doesn’t listen.

datavirtue 2y ago
That's why it's your fault, because you won't make decisions. You feel like there are rules and guardrails constraining you and bringing order to society but it is not so. If you envision the reality and live it, then it will manifest. Some people thinks this means being forceful and demanding. Just the opposite. Then again, I doubt the company has a reward structure in place that even makes the mental energy worth expending. If you aren't on the way up, then you are on the way out.

toast0 2y ago

> In every single company I have worked, the process always took priority. If process (or freedom from process) is important to you, you need to make it a priority when you're interviewing. May depend on what industry you work in, of course, some industries don't have any cowboys. That said, I like my cowboy jobs with a little bit of process. What's deployed in production should be reflected in source control, but I'm not a stickler for which comes first. A change notification should be posted before production is changed, but if you have separate push and load steps, you can push before you notify (if pushing takes a while, it's good pipelining to use the push time to compose your change notice). Changelogs usually shouldn't be 'bugfixes' or 'latest', but 'fixing' is appropriate for a close in time followup. That's process, even if an ISO compliance officer would lose their mind.