hn_acc_2
My interview with Meta was exactly as you described (a CS riddle taken from a textbook, to be solved without running the code or receiving hints). But in my interview with Amazon, each coding interview also included a couple leadership questions. If you want you can look up the exact questions that they'll give you to test what they call their "Leadership Principles"
Also the Amazon coding questions were not taken directly from Leetcode, and were easily reasoned out without prior knowledge of a special algorithm.
These sort of people can work the very foundations of the company into an ungodly quagmire that would send you screaming back to the fad-chaser dev in a heartbeat.
Also despite the meme, most mid-senior devs are actually keen on making their contributions valuable to the business, having gotten over this phase of fascination with new tools
Whether or not a "good build system" should handle it, the fact that single-file libraries are much preferred these days should demonstrate most people don't have such a build system
2) Most developers just want to compile to a single binary. Any developer who for some reason needs separately compiled objects should be able to quickly achieve that from a single-file library
[1] https://github.com/phoboslab/qoi/blob/324c2243b2fb35f741a88d...
The people mentioned specifically in the comment are of more concern; sales, admin, etc. salaries in this field are also inflated compared to other industries.
Shopify is the first one I've seen, so I don't think it's quite as common as you are implying, but I'm curious to know what other bad behavior you have found
It seems to me that it's just the first one that everyone's grandma has heard the name of.
Some journalists will say BTC is just the "most stable" but the fact that it has the most miners is just a consequence of the high price, not the other way around.
As for the technology, what is actually maintaining BTC dominance in the crypto world other than general first mover sentiment?
Now we add additional complication "OK, these pip package authors have upstreamed Alpine packages, and these other ones are only on PyPi".
Maybe this approach would work if you can keep your Python dependencies to a small list of well-maintained packages
Their use of musl libc makes it a very poor choice for running python in a container, because it forces a lot of manual rebuilding since the PyPi wheels don't work on Alpine, among other issues [1]
Can anyone translate this for me? This sounds like someone throwing a bunch of big words together to me.
I don't have a Nature subscription but this seems like another non-study, 80 adults in a contrived experiment with flashing images then given a "questionnaire" with which conclusions are drawn...
Nobody writes performance-critical code in pure python.
Not sure how "tooling" is bad, what would you say is limited there?
Package management, again, what package management problems are unique to Python? Many people say this but it seems the problems they bring up are not unique to pip or the python ecosystem, same problems are found with rubygems, npm, Maven, etc...
Maintainability is a responsibility of developers and not a programming language, and unmaintainable code can easily be written with any language. However I'd argue Python should score positive points for maintainability; one of the languages I feel most comfortable picking up old code from someone else and groking it easily.
But as a general rule, the programmer will have a hard time "outsmarting" the compiler by using different objects or abstractions.
Compiler authors have spent many hundreds of combined hours making C code run as fast as possible, and optimizing the switch statement is something they've most certainly done to death.
I.e. if your control flow is switch-case-like, use a switch-case.
All of the moonshot projects are done at the direction of executive leadership in the hopes to open new profit streams.
In fact some of the more technically promising projects (like Servo) had their whole entire team laid off recently to "refocus" on more of these executive-sourced profit grab moonshots
I still use it with a super oppressive jail time and few retries, with a few whitelisted IPs and it seems to work ok.
1) Costs were not zero for the re-release. The only version of the game data (stats, items, enemy spawns etc.) was in the form of an original database backup (from an old employee's personal stash!). Classic runs on the modern WOW engine, so work was required to shoehorn the old data in and reimplement systems and interfaces which don't exist in the current WOW engine.
2) Before Classic's release, by far the most vocal crowd making demands of Blizzard were shouting their slogan "NO CHANGES". I really don't find it surprising that Blizzard has not made major changes since the majority of the player base requested as such...
So too do students with authority issues enjoy exerting newfound power over the authorities they oppose by complaining to their risk-averse boss.