97 karma · joined May 15, 2012
Convenient date range considering the global pandemic and WFH shift …
What I find interesting about this is that looking through the lens of ones ego, this seems like the logical way you would cope with losing a job - just convincing yourself it wasn’t ever really what you wanted
Statements like this are, exaggerated, to say the least. While the DX7 is undoubtedly prolific in 80s pop, it was just a synth that was successful for its price point (and timing!) as called out in the article. Case in point that today, nearly all the major manufacturers are building re-issues and the most coveted are those the analog counterparts of the Dx-7 (the sequential prophets, Oberheims, ARP...). FM has no way succeeded the typical subtractive synthesis of the analog machines.
source: I write 80s influenced music and collect synths
For me it was important to acknowledge this and help myself set boundaries to how I spend my time producing. I also found myself gravitating toward vintage gear because of its limits and how it enforces decision making (e.g. printing synths directly in audio, which was a game changer in terms of process)
In my experience this rings true for senior roles and less so for new college grads.
Companies seem afraid to hire thinking there is a slightly better/cheaper option around the corner.
I can see why perhaps a candidate receiving a rejection may think this, but in the companies I’ve worked at this has never been the case. It’s always been “it’s really tough finding talent, not paying talent”.
The take home assignments with random marking standards. Tests can matter, ui could matter, api structure could matter, documentation/choice of framework, speed, style all could matter but you rarely know which matters to whom and rarely have time to do it all and even if you did everything perfectly a lot of the time no one even looks or the reviewer expects the code to look like how they might write it.
A fair reviewer recognizes the limitations of these take home exercises. While there are many ways to perform a take-home successfully, there are more ways to show that you aren’t qualified for the role. Not all that pass will be right for the job, but most who fail aren’t.
The article acknowledges that the root cause was an existing bug in Package Manager.
It's dependent on the function attributes of memset (e.g. __attribute__((pure))) - it won't always be optimized out.
https://www.cs.auckland.ac.nz/references/c/gcc4.7/Function-A...
1. http://books.google.com/books?id=5OZblBzjsJ0C&pg=PA181&lpg=P...
With that knowledge the solution seems pretty intuitive.
Sure, advertisements seem like the end game, but how will they be targeted? How can they be implemented without severely affecting application experience and user expectations?
If the engineer who develops this (provably optimized) codebase can't read the code, he/she should be replaced with someone who can.