2020 has not been the best year ever but with more time at home and less time commuting I did find time to read and discover more online. The following is a list of the best resources I have found while trying to become a better developer in the second half of 2020.
- Good News
- Coding Music
In the second half of this year, I discovered Indie Hackers. I really like the content and ideas there. If you are looking to work on a side project it’s certainly worth a look.
A brief list of the best tools I discovered and used recently.
When I worked at Spotify I was blown away by the internal tooling and how quickly I could get set up and deploying code. I got to use an early version of the developer portal there which has since been opensourced. We are using this at my company now and it’s really worth a look if you want a nice way to do internal tooling.
Most access tools I’ve had to use kind of suck if your job is actually making stuff (looking at you Cyberark). Hashicorp Boundary looks like a really promising alternative so far.
GitHub CLI is a great tool and a lot of fun to use.
A browser for devs that is very cool.
VSCode has had Live Share for a while. A lot of people prefer Jetbrains tools though so I was happy to see this: https://www.jetbrains.com/help/idea/code-with-me.html
This article encouraged me to make this list https://www.learninpublic.org/v1-principles-learn-in-public.pdf
If you want to learn about using GCP (Google Cloud Platform), QwikLabs is a great resource where you learn by doing.
repl.it is a site that seems to consistently deliver amazing content and is also a very nice site to use. I recommend signing up for the newsletter.
I am not looking to interview soon but I suffer serious interview anxiety. To help reduce the stress I practice as often as I can. I love the 30 days challenges at LeetCode. My last attempt (I didn’t finish the month) https://github.com/ruarfff/leetcode-typescript-practice. Will try again in January.
I love to code games but I haven’t done much of that since college. I get to dabble a little in it using Screeps. An RTS game where you code the AI for your units. It’s a lot of fun and good coding practice.
This is my admittedly poor attempt so far: https://github.com/ruarfff/screeps-scripts
This massive list of resources to learn and practice with:
Just some good tech news I came across recently.
I love Hashicorp. I for sure might be wrong but I consider this good news for people like me who spend a lot of time automating deployments and I am very much looking forward to trying it out: https://www.hashicorp.com/blog/announcing-waypoint
I could watch GeePaw code all day. There’s something so modest and natural about this series. It doesn’t make me feel stupid and I am learning a lot from it: https://www.geepawhill.org/series/real-programming/
Rich Hickey is a great speaker and clojure is my most favourite language I never use for anything:
If you have been struggling to get going with machine learning despite lots of Coursera courses done, the insights here might be interesting to you:
Despite all the improvements in hardware, software performance, in general, doesn’t feel like it has improved at the same speed. This is an interesting read on that subject: https://fabiensanglard.net/silicone/
Something I used in college but only rediscovered recently https://processing.org/. It’s a very interesting project to help with visualisations in code.
GeePaw is great. These articles are particularly good ones I read recently:
If you have worked in a “big corp”, you have almost certainly encountered bad COTS (“commercial, off the shelf” software): https://sboots.ca/2020/09/16/fake-cots-and-the-one-day-rule/
Pretty much every article by Kent Beck is great. This is a good one I read recently: https://medium.com/@kentbeck_7670/monolith-services-theory-practice-617e4546a879
A reminder about the risk in crypto: https://decrypt.co/51692/a-crypto-user-sent-50000-to-a-smart-contract-its-gone-forever
Generally, I am not a fan of the “why I left some big tech company” posts but there was something really nice about this one: https://mtlynch.io/why-i-quit-google/.
Some tips on working on a side project while not immediately having to quit the day job: https://www.indiehackers.com/article/f7697df2d7
If you ever worked at a “big corp”, you have probably encountered pain with certs on the network. This series helped me understand this stuff better and I learned a bit of rust too:
Bit of a cheat here since this site isn’t really on tech but it isn’t 100% not tech either and I love it a lot: https://www.brainpickings.org/
I listen to a great many tech podcasts. One I discovered late in 2020 is the Idealcast and I highly recommend it for its positivity and thought-provoking content:
I was lucky to get to go to The DevOps Summit in October. The focus was largely on dealing with problems in large organisations and more on culture than tech but this is a problem I care a lot about lately. I really loved this conference and how they made the virtual & remote aspects work well. I loved chatting with the speakers in slack for example.
I also got to attend GitHub Universe. It’s one of the most fun conferences for developers I think as you end up trying out so many new things at it. They have done a great job of going virtual too.
When I was at the DevOps Summit I attended a talk by Mark Schwartz and learned about his new book The (Delicate) Art of Bureaucracy. It’s not the kind of book I would ever have thought to buy, to be honest, but the talk was so entertaining I decided to give it a go. It ended up being one of my favourite books this year. If you struggle with bureaucracy in any aspect of life, you will likely find something useful in this book.
Brain melting assembly problems https://www.xorpd.net/pages/xchg_rax/snip_00.html. I can’t really review this book except to say it hurts my brain but I still love it. It’s free but you can support the author by getting a hard copy.
I got into coding late in life and really messed up in my younger years by completely ignoring maths. The book Math for Programmers has helped me catch up a little bit and fill in some of the gaps in my knowledge left by a squandered youth.
I read the first edition of Release It! by Michael Nygard about 5 years ago and it changed how I thought about running apps in production in a big way. I am now reading Release It! Second Edition and I am learning just as much again looking at it with more personal experience and enjoying some nice updates in the book.
Some amazing CSS https://tholman.com/obnoxious/
All your programming pain in one video…
The only gadget I bought for my dev setup in the last 6 months was this keyboard: https://dygma.com/. It is absolutely amazing.
This just looks so cool and I want one: https://www.clockworkpi.com/devterm
On needing a good strategy and vision from your leadership (a thread):
a big learning the last year is the degree to which your most passionate team members will *expect* leaders/managers to coherently frame strategy— John Cutler (@johncutlefish) December 13, 2020
this is where "autonomy" often hits a snag. Leaders assume it means "bottom up" planning. But that isn't it ... (1/n)
On things going bad in a rewrite and sunk cost fallacy (a thread):
So a team was formed to build a new mobile architecture for this new app. The driving charter for the team was to build an architecture that would “sustain mobile development at Uber for the next 5 years”. We did both platforms at once. Product and Design also started over.— McLaren Stanley (@StanTwinB) December 10, 2020
A profound thought on hackathons:
Companies think, “oh, we should have hackathons!” and miss that _actually_ they should have an organization where hackathons are worth having.— Beth (@bethcodes) October 25, 2020
It’s always DNS:
Interesting war story (a thread):
Back story.— John Cutler (@johncutlefish) October 3, 2020
Way back I worked in a PPT factory at an investment bank. Our job was to assemble “decks” for investment bankers. The operation ran 24hrs a day with dozens of “operators”.
Young bankers would work CRAZY hours.
On being an opensource dev:
Them: I contribute to open source.— Jay Phelps (@_jayphelps) September 29, 2020
My productivity algorithm is something like:— Sean Carroll (@seanmcarroll) September 17, 2020
* Start to do something
* Remember higher-priority thing, switch to doing that
* Remember that high-priority thing is hard
* Do nothing
GraphQL VS Rest:
Someone shouted “GraphQL is a better REST” and then this happened pic.twitter.com/eHO36cUAit— Marc-André Giroux (@__xuorig__) September 9, 2020
How I felt when I saw JSS:
js devs applying js solutions to css problems pic.twitter.com/umxJJgt3Yf— I Am Devloper (@iamdevloper) September 8, 2020