Earlier quoted context omitted.
Twitter is a private company now. There are no more stocks to vest, so the idea that this is to dodge vesting schedules doesn't make any sense whatsoever.
Until recently I worked at a private company with a stock vesting plan.
Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
961–970 of 1001 posts
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#962Earlier quoted context omitted.
Twitter is a private company now. There are no more stocks to vest, so the idea that this is to dodge vesting schedules doesn't make any sense whatsoever.
This doesn't make sense. There are certainly options and stock to vest; every pre-IPO startup employee in the world knows about the four-year vesting schedule.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#963Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#964Earlier quoted context omitted.
People despise him in HN? Have you looked at the comment section? Looks like the exact opposite to me.
He means "why doesn't everyone like him"
And your post is part of the problem. Because I’m not Musk bashing, you assume I’m on the other “side” and must be his fan. You’ve condensed the world into a binary operation. I’m more annoyed that he gets all the attention he gets. That’s all.
If you don’t like him, the best thing you could probably do is not let him live rent free in your head.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#965Earlier quoted context omitted.
Twitter is a private company now. There are no more stocks to vest, so the idea that this is to dodge vesting schedules doesn't make any sense whatsoever.
According to blind, vesting schedules are converted to cash grants on the same schedule. So essentially there is still vesting, and no acceleration for regular employees. Curious to hear if anyone knows otherwise. https://www.teamblind.com/post/Twitter-Accelerated-Vesting-L...
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#966I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…
I suspect it’s less a complete review and more an interview of the senior technical manager, to get a sense of whether they are up to par. Do they think about observability, alerting, refactoring, service architecture, etc. reasonably well? Are there issues with how they motivate their teams or when they give them responsibilities? Are timelines challenging but doable? “Code” is most likely “architecture” and “archit…
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#967I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…
Yes, software is typically more complex than a laymen would expect once all of the edge cases and layers of legacy code or “guano” are implemented. However, I doubt that these outside developers are expected to understand everything in a single day. There are legitimate questions regarding how certain sections of the Twitter code operate as it relates to censorship, which is a primary reason Elon purchased Twitter. G…
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#968I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…
I suspect it’s less a complete review and more an interview of the senior technical manager, to get a sense of whether they are up to par. Do they think about observability, alerting, refactoring, service architecture, etc. reasonably well? Are there issues with how they motivate their teams or when they give them responsibilities? Are timelines challenging but doable? “Code” is most likely “architecture” and “archit…
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#969Earlier quoted context omitted.
> I don't think they can get a clear picture by looking at last 30 days of code I can very quickly spot developers who are mediocre or worse by looking at their last 30 days off code. (As long as it's a language I have decent experience in.) I suspect he's trying to access the team's technical competence.
No you can't because being a good developer isn't always about smashing out code, I've easily spent 30 days with great developers talking about planning and implementation before much code is written. Hopefully it's not you who is the mediocre developer?
Things like: State in strings instead of properly defined enums / data structures. Magic numbers instead of constants. Dangerous error handling. Compiler warnings. Missing or incomplete input checking. Anything vulnerable to SQL injection, or similar. Significant copy and paste within the same codebase.
When a developer with more than a few years experience writes code like that, (except in throwaway situations,) then there's a clear problem.
More subjective signs of a poor coder are: Super long methods, (or too many sort methods.) Passing around a single value but always picking a new variable name. Inconsistent naming conventions. Sleep statements to fix race conditions. Unnecessary special cases. Incorrectly using an ORM. Code that is many orders of magnitude slower than need be. (IE, sucking the entire DB into ram for just one value.)
Some language specific warning signs: Lots of "unsafe" (pointers) in C#. Lots of unwarps in Rust. Bounds issues is c/c++.
Re: Tesla engineers were on-site to evaluate the Twitter staff’s code, workers said
#970I worked at Facebook and remember what it was like to first face the total complexity of the system. It’s really hard for me to imagine myself working at a company that deals almost exclusively with machine-generated data (as Tesla does) and being assigned to judge a social platform’s engineering qualify in one day . Cars and spaceships on a closed network are fundamentally “clean” compared to having hundreds of mill…
I suspect it’s less a complete review and more an interview of the senior technical manager, to get a sense of whether they are up to par. Do they think about observability, alerting, refactoring, service architecture, etc. reasonably well? Are there issues with how they motivate their teams or when they give them responsibilities? Are timelines challenging but doable? “Code” is most likely “architecture” and “archit…