Weekly Review 2018 Weeks 1–2
This is my first weekly review in this year. (And first one after a long pause.)
These two weeks:
- 8,760 hours
- Meltdown and Spectre
- You don’t have to be that busy
- Sleeping well
Total articles read: 25
8,760 hours. Absolutely awesome.
- always get enough sleep
- wake up at fixed time (which shifts with daylight time, though)
- use light to get up
- don’t sleep in after long night
- compensate with naps
- learn to nap properly
Why you focus on short-term goals instead of long-term ones.
Meltdown and Spectre
- Finding a CPU Design Bug in the Xbox 360. While not really about Meltdown/Spectre, but describes finding of a similar bug in Xbox 360 CPU.
- Intel CEO Krzanich sold shares after company was informed of chip flaw
React / Web development
- React Stateless Functional Components: Nine Wins You Might Have Overlooked
- The Top 66 Developer Resources From 2017. Not exactly about web development but mostly about it.
- To Serve Man, with Software
- go channels have bad API (throw panics, non-symmetric)
- channels block (which makes them hard to use with mutexes and other traditional synchronization primitives)
- not powerful enough
A post about asynchronous programming, async-await, generators and green threads. (Green threads been the best.)The post does not mention Haskell, but it has green threads, too.
Go to chrome://flags/#smooth-scrolling and disable smooth scrolling feature.Well, this does not fix my lag, but made it less frequent
Rust compiler team has structured the year to include an “implementation period,” when they particularly focus on compiler implementation. Here are some notes on what worked well and what didn’t. In particular, focusing working groups on goals rather than compiler parts is a nice idea I like.