Comment on What are some common misconceptions about programming that you'd like to debunk?
okamiueru@lemmy.world 9 months agoIt was the job switch that landed me in that situation. A change from a small company where about 70% was actual productivity, to a large corporation, in a team where there was severe issues with planning and working on the correct problems. So far it’s been 6 months of… well, wondering if I’m missing something, or a bigger picture somewhere, to trying to turn the ship in the right direction. If it’s still like this in another 6 months, I’ll consider a change of scenery.
Daxtron2@startrek.website 9 months ago
That’s fair, that definitely can happen with a switch. My first year at my current company was like that and occasionally still is lol. Luckily our next few quarters I’ll be on a team that has much nicer processes so I won’t be twiddling my thumbs waiting for solid requirements.
okamiueru@lemmy.world 9 months ago
This is exactly the situation. Except that my team consisting of consultants just “started”, instead of trying to scope out the constraints and larger picture.
Six months, and the result so far is a fairly uninteresting exploration into a happy-path use of some technologies, barely related to the task missing requirements, and as it turns out, unsuited for it. Boggles the mind how much resources are wasted on such things.
Daxtron2@startrek.website 9 months ago
Yeah I would not like that situation at all. I was very adamant about not starting our latest project until we had firm requirements. Of course that didn’t happen but I was very careful about designing in a way to be flexible enough to change to requirements. Had a major change halfway through but only lost a week or two which could’ve been much worse.
okamiueru@lemmy.world 8 months ago
Only losing a week on a major change is a good sign. I wish the people who started the project had that same attitude with regards to clarifying requirements. They did however the opposite of designing a flexible solution. No thought to the actual problem, picking a contrived problem to “tackle”. Full on blinders on event driven architecture, split a simple thing into multiple nano-services, yet tightly coupled by sharing the same model which is de/serialized, and then throw in application level filtering on the events… no schemas, no semantic versioning.