374 karma · joined October 21, 2014
(Oh, and of course, am not saying this is the only strategy for dealing with psychosis, but it is just that it was also the first thing that came to mind when I read this article:)
This now makes sense you were able to work on Rosetta 2 mainly on your own!
... not to mention all the performance considerations and optimizations, also requiring a strong sense of algorithms and computational complexity. Wow!
Yeah, seems like most mathematicians (and physicists) I know who go into tech don't get past learning a couple of programming languages and don't have an interest in learning the depths of a how a computer works. Very impressive!
IMHO, if you have a great product and a market with significant demand, seems like eventually the customers will come - and it seems like this is possible if Intel can retain manufacturing leadership for a few years and build out a better ecosystem to support external chip development by foundry customers, but this of course take time.
https://semiwiki.com/forum/index.php?threads/intel-18a-too-g...
And obviously, many of these posters are like me and have a bias towards Intel succeeding. Still, it sounds like 18A seems like it's on track in terms of the technologies (at least for now)
https://semiwiki.com/forum/index.php?threads/intel-18a-too-g...
But of course, the sources may be biased/overly-optimistic/hiding-info.
Becausefrom what I've read on forums, by all accounts from the insiders, the technology behind 18A is incredible (gate all around transistors, backside power delivery, 3d Chip stacking...) and that in a year or two ,it should put Intel manufacturing a little ahead of TSMC.
Although, have also read that the one problem is that even 18A won't be profitable for a couple years. Yeah, that the problem with Gelsinger's original plan is that 3 years wasn't enough time to get to profitability, but 5-8 (but that it still is a good plan).
But have also ready that to make this profitable is like a 5-8 year plan, not something that is profitable in 3. To me, this is his biggest mistake, he needed to keep the ship sailing at least somewhat smoothly while waiting for this big gamble to pay off.
And eventhough I do agree with you that he made a lot of mistakes, still he got the the most important issue right, regaining manufacturing leadership.
And most teams get the core ideas right in my opinion: small, tight knit teams working closely together, with a "reduced amount" of process (yeah, think the number of meetings in agile is bad, in waterfall, meetings seem like crush you like a tsunami).
Specifically then, as a technical person, this means you don't ignore the requirements and just think about the code. Instead, you need to communicate with both your higher-ups and your end-users, in order to make sure the code you're writing matches their needs - in my opinion, requirements is the part that most developers are weakest in, but if they strengthen would make the biggest difference. Get it as close as possible to being right on the first time (it's very rare that this happens but focusing on doing really good requirements increases your chances that you don't create the wrong system).
Btw, I actually don't have a child so haven't used parental controls, but just found out that they do have an app time-limit setting: https://support.apple.com/guide/iphone/set-up-screen-time-ip....
yeah, I have an app blocker on my iphone to block news websites/apps called Freedom. Essential these days to staying productive - although, don't think this app would work for your child, because it is not very reliable and needs to be restarted every few days.
... although, even if this is true, this could just be that kids seem to be more attached to their parents then they used to be (have read this as well).