“Code reviews” ..
Ulterior motives?
Wow that's some great engineering, solid experience leading a large-scale project with 10M loc+ for sure. He must be a c++ wizard to implement such a gem.
I bet it was more of a rollout complexity. Dependent systems etc.
Database column size. Data warehouse and query assumptions. Database scaling. Server scaling. UI/UX concerns. Pre-launch testing, user testing, A/B testing, post-launch analysis, rollout plans, rollout db migration, rollback plans, rollback-db-migration plans. Optimization and compression changes. Places that maybe stored length as a single byte and now need to be 16 bit potentially. Meta took 4 years to fix messenger saying you had messages when you didn't.
10 years at a company and all he did was update msg from varchar(140) to varchar(280); he would have been pipped by 6 months at Amazon.
Sarcasm, I hope?
I hope this is sarcasm. Seriously… if not.. please resort back to your banana stand. If blind wasn’t anon and you are serious. You would be pipped in the first minute at Amazon
I forgot Tweeps lived in a bizzaro land... You think 280 characters gives you more space to express yourself.... Imagine 560 Either way still feel for what's going on over there
so because an engineer lead a feature development 5 years ago he is untouchable for the rest of time and can do nothing to warrant a lay off? lots of information missing.
He might of not actually coded in last 5 years. He probably was in technical management more than than making new code.
yes i agree. the feature these tweets are talking about was rolled out 5 years ago. my guess is that a firing is based on current contributions and impact, regardless what he did in the past, which is the way it should be. again a lot of missing info but would you want a company full of engineers who ship one important feature each and then hang their hat on it and coast?
@Northrop Grumman I've seen you in multiple threads simping for Elon. FYI everyone
Plan is going well.