3 ms·
I haven't been writing code professionally really long but one thing I notice is "It" ... even the same "It" can be dramatically different wherever you go and n
by duxup 5y ago
I haven't been writing code professionally really long but one thing I notice is "It" ... even the same "It" can be dramatically different wherever you go and not everyone seems to be entirely aware of that or able to adapt.
You get folks who maybe have worked a few places, or a lot of places that all operate with the same bureaucracy / processes and they seem unaware that it could possibly be different anywhere else.
Some folks I know work at a very large corp. Their development cycle is very heavy with processes, albeit seems very reasonable / works for them. Folks writing up what some feature should do for 100 different possibles, folks reviewing it in some way ... on and on. Maybe someone finally writes code and everyone reviews it. Testing, testing, testing. I'm not judging it, it's just ... a lot.
I work at a place with 3 devs, and only one other really does what I do. I get a vague idea of a feature requested, I talk to the customer, I go write it. Show some folks, maybe I change things, maybe not. I roll it out. Done. Feature is out there in production, live, sometimes in just a few hours (and I watch our error reporting system to see if it blows up or not).
It's a completely different mindset / process. I've worked with folks who worked at very large corp and they weren't doing anything differently than I do, but in my more informal / not a lot of review environment they struggle. They're good, they're not bad, they just are so used to so many eyeballs / not used to talking to customers (and distilling what they say) / they're used to so much confirmation that they freeze up in a way. They can do "It" it's just "It" in a new context is hard.
Granted I might struggle in a more formal environment, I don't know I haven't tried it.
But the same "It" is not the same "It" everywhere.