Hacker News new | past | comments | ask | show | jobs | submit | deepakkarki's comments login

> Overall, we expect to reduce our team size by around 10,000 people and to close around 5,000 additional open roles that we haven’t yet hired.

Wait so does that mean they'll end up with 10K less after hiring 5K folks? Which might imply that they'll be firing 15K people.


They are firing 10k people they have already hired, and not hiring for 5k roles where they haven't yet hired. So 10k are leaving, and the planned 5k they were going to add will not add. This means they are losing 10k.


No, it means that they won't hire these 5K in the first place.


I'm reading it as 10,000 people being fired and 5,000 job openings, some of which may have offers out, being cancelled.


No, it means they will not hire 5 k people they had planned to hire, and they'll let 10 k people go within their current workforce.


Well, that just depends on the programming book? If you pick up TLPI it will talk about stat and inodes. Pick up a book on perf, it will talk about syscall overhead, etc


I don't think that's a fair comparison. It's more like would you want your physical ailments treated by an unfit but talented medical professional or the fittest person at your local gym?


Or the difference between conceiving a child and raising one :)


I always smile when a green field project starts and then they claim its “Clean Code”. No, you won’t known if it was clean code until years down and the system will need updates. Then and only then you can reflect and see how hard it was to changes things in it.


Fully agreed. No matter how "clean code", the next person or team is immediately going to label it "legacy" and complain endlessly about all the choices made by the original author(s).


Many dependencies? Updating them is hell, remove dependencies and just write the utilities we need so we can update to latest easily!

Few dependencies? Too much reinventing the wheel, delete all that code and add dependencies!

There is no perfect code, can always make different trade-offs and move things around.


My metric for clean code is how quickly a developer unfamiliar with it can understand it


It seems that anything successful, for any given era, is the one thing that minimize time to understanding better than others.


Much as we denigrate COBOL, that is still its greatest advantage. Yes, it's wordy, yes it's old. Yes, it needs to be really updated. But it's still easier for a new hire to understand the COBOL old code than any other old code.


I've never had any problem digging into any Python codebase.

Even magic stuff like `@attributes` is easily searchable.


I mean, a green field project is about as clean code as you can get. It's (reported) bug-free!


raising someone else's that is already 4yo and emotionally harmed


This hits home. You win.

Maintaining and cleaning up a mess someone left behind are two different things.


Whenever I do a big refactor it’s so that it will be messed up my way instead of being messed up their way.


Ha, love this one.


aaron695 is not downvoted, s/he is shadow banned.


A terrible shame how HN shadow bans people. Wouldn't be using it if I didn't remember that this is a site operated by ycombinator with objectives other than facilitating an open and and inclusive social network. Violates the basic principle of decency on how you should treat others the way you want to be treated. i get why and accept it in a way, doesn't mean I like it.


This was the core motivation behind why I started https://www.discoverdev.io/

Ran this for about 4 years before I called it a day earlier this year. Got busy with graduation and job searching! I do plan to start it again after I find a job and settle down :)


I followed this for a long time! Great work.


Reminds me of this famous "Juice it or lose it" conference talk - https://m.youtube.com/watch?v=Fy0aCDmgnxg


Well the companies choose to own the network and run closed protocols. They are not just running a free service but gatekeeping an whole audience.

Either have standard open protocols or be regulated.


The classics should be available outside of scihub!

For example, Prior Analytics http://classics.mit.edu/Aristotle/prior.html

Most famous papers are available via Google scholar!


I think you mean "the list is not supposed to be exhaustive"?

Unless I'm reading it wrong....


That is indeed what I meant.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: