2 ms·

But how much typing, how much staring at screens, how many meetings are needed to reach your actual goals? I care about the choices bc the wrong ones create pro

by abeppu 5y ago

But how much typing, how much staring at screens, how many meetings are needed to reach your actual goals? I care about the choices bc the wrong ones create problems which require more typing, or typing at night. "The job doesn't change" except the amount of time and effort required to do something useful can change.

nkingsy 5y ago
Sure, but that’s not my problem as a new hire. I just assume any new codebase will be horribly sticky and hope I can smooth it out a little. Humans calibrate so quickly. With my latest job, I spent the first month thinking I was coding my way through a nostril-deep vat of honey and getting nothing done, but my boss was impressed with my productivity. Now it’s just normal and I feel productive again though the pace hasn’t changed. Startups go faster, big companies go slower. I’d much rather get paid well and navigate intractable tech debt with zero pressure to work extra hours than move quickly and get side eyes for stopping at 5.
dragonwriter 5y ago
> how many meetings are needed to reach your actual goals? Basically zero, other than requirements gathering meetings with customers, the number of which are required is independent of tech stack. Other meetings will probably happen due to process choices made by your org, but they mostly don’t (1) depend on tech stack, or (2) contribute to reaching the actual goals, except insofar as they are necessary to clear arbitrary impediments also created by organizational process decisions. > I care about the choices bc the wrong ones create problems which require more typing, or typing at night. Unreasonable working hour demands are not a product of tech stack choices, they are a product of management disrespect for staff. You cannot avoid them by choosing the right tech stack.

2 ms·

But how much typing, how much staring at screens, how many meetings are needed to reach your actual goals? I care about the choices bc the wrong ones create pro

by abeppu 5y ago

nkingsy 5y ago
Sure, but that’s not my problem as a new hire. I just assume any new codebase will be horribly sticky and hope I can smooth it out a little. Humans calibrate so quickly. With my latest job, I spent the first month thinking I was coding my way through a nostril-deep vat of honey and getting nothing done, but my boss was impressed with my productivity. Now it’s just normal and I feel productive again though the pace hasn’t changed. Startups go faster, big companies go slower. I’d much rather get paid well and navigate intractable tech debt with zero pressure to work extra hours than move quickly and get side eyes for stopping at 5.
dragonwriter 5y ago
> how many meetings are needed to reach your actual goals? Basically zero, other than requirements gathering meetings with customers, the number of which are required is independent of tech stack. Other meetings will probably happen due to process choices made by your org, but they mostly don’t (1) depend on tech stack, or (2) contribute to reaching the actual goals, except insofar as they are necessary to clear arbitrary impediments also created by organizational process decisions. > I care about the choices bc the wrong ones create problems which require more typing, or typing at night. Unreasonable working hour demands are not a product of tech stack choices, they are a product of management disrespect for staff. You cannot avoid them by choosing the right tech stack.