Re:Is revenue model more important than culture?
by rootusrootus on Monday September 21, 2020 @01:02PM
(#24545784)
This is where I am with my current gig. We are abstracted so far from the actual user that it feels like a useless amount of urgency for no particular reason. And middle management is more experienced in hardware than software, so they keep trying to use the "we will just hire more contractors to make it happen faster!" strategy. Feels like needless stress to build something nobody is really going to use anyway. And on top of that, I don't even get to do any code, I'm too senior, so all they want me to do now is draw up architecture diagrams.
I'm thinking about jumping ship and taking a pay cut if necessary just to get back to something where I can actually solve real problems building software I know people will actually use. It's so much more satisfying to work on something you know is useful.
Re:Is revenue model more important than culture?
by runawaybottle on Monday September 21, 2020 @02:29PM
(#24546781)
But I will say, this is a ‘us’ problem, not necessarily a ‘them’ problem. I guess this job requires dealing with the nebula.
It’s not easy, but the feelings are valid.
Re:Is revenue model more important than culture?
by tboyd47 on Monday September 21, 2020 @12:13PM
(#24545093)
Ah, I've been there. I call this "rapid bozotyping" :D
Hope you find something better! What tech stack do you work in?
Re:Is revenue model more important than culture?
by dvtrn on Monday September 21, 2020 @02:23PM
(#24546705)
I call this "rapid bozotyping" :D
I would read an entire research paper dedicated to this topic if it existed, heh.
Re:Is revenue model more important than culture?
by runawaybottle on Monday September 21, 2020 @12:16PM
(#24545138)
The favorite tech stack for bozotyping, React/GQL :p
Re:Is revenue model more important than culture?
by dmoy on Monday September 21, 2020 @12:17PM
(#24545155)
It is a nice reality check where if you break something too bad, you have tens of thousand / hundreds / millions / ?? people breathing down your neck in like a few hours.
I never really considered that without that it would get too loopy.
The second half of my career, even at larger places, was building MVPs where you go forever without a single user ever seriously using it.
This duality in my work experience created an odd existential crisis. Push to prod after awhile felt like fake urgency. Ideas being thrown around by team members after awhile felt like needlessness. New hires and growth initiatives felt stupid, we barely saturate the existing team. Demos/Presentations felt futile, with a part of your soul just screaming ‘Who the fuck uses this!’.