318 karma · joined February 1, 2023
It's not really clear what you do with a staff+ long-term IC. A lot of them don't want to manage or be involved in leadership, but they want to pull down a huge salary and just do work that is frankly replaceable by a senior eng.
To be clear I do believe there are levels of IC experience above staff, but being 21 and joining a startup doesn't make you a Principal Engineer just because you hung around until you're 30. Especially if you've only worked at that one startup.
A lot of people have blind faith in just extrapolating numbers out into the future with no context.
Respectfully, in your post you literally say you got a new manager who PIPed you for being hard to work with. The whole tone of the article feels like rehashing old disagreements.
One tell-tale sign is endpoint security and using his own device. It's the kind of permissive cultural thing that does not scale because of compliance issues and developer productivity overhead. But it's very hard to wrench these long-time devs away from their preferred Linux distribution which requires conditional build stuff everywhere to support. Use a work computer for work, let them monitor the updates and stuff, as long as they're not using the webcam to record you who cares?
The database backup story - my guy you were on the database team. Backing up the databases is job 1. You can't just passive-voice away "oh there were no backups". But of course he's more interested in fighting about sharding architecture than actually keeping the site running day-to-day.
His big takeaway is that Gitlab didn't spend enough time on performance for their hosted offering which was a huge money loser. Just because he thinks performance stuff is fun to do, if the hosted offering is a money pit of course they're not throwing more resources at it. You have to make an actual business case for why your thing is more important and makes money more than another project. You don't just engineer in a vacuum for the fun of it.
The alternative is requiring Congress to write every single rule explicitly and pass a law adapting to any change in circumstance or technology. In practice this means "no regulation" because Congress is pretty slow and adding more detail would only make them slower.
If a touchscreen was the ideal way to interact with a car, why aren't acceleration and braking done through the touch screen? Why isn't steering on the touch screen?
I'm not saying to go back to the stone ages, but ultimately there have been movements to buy local and preserve traditional ways of crafting that are push back against industrialization.
For someone who's had so many successful movies you'd think they'd defend him to the hilt if he was innocent?
https://www.hollywoodreporter.com/news/general-news/john-las...
In theory it provides better incentives for both parties:
Customers don't have to pick instance size, etc. to try and accomodate their workload. They can buy throughput, etc. in fractions of an actual instance. They can look at their quota usage to determine whether to "scale up" or "scale down".
Service providers are incentivized to optimize their software. If you sell instances + a service on top, there's a perverse incentive not to make your code too fast or people will buy fewer instances. In serverless, providers are incentivized to reduce their costs and optimize the entire stack.
Scale to zero isn't necessarily a property of serverless - a service provider can agree to keep your data on ice for free, but that's a business decision.
It's not foolish to imagine the world could be better.
If Bird was a "constellation of small businesses" those businesses could take their scooters to a competing network, or start their own local scooter share. Bird retained ownership of the scooters in what sounds like a very lop-sided and exploitative agreement.