|
|
February 10 · Issue #5 · View online
Curated commentary on articles that help you grow as a professional.
|
|
This edition’s content focuses on career, money and market. I have learned quite a lot this time. Enjoy:
|
|
Why You Should Have (at Least) Two Careers
By committing to two careers, you’ll be less specialized but best at the combination of both. The author tells a personal story how this works out for him being a trader, a music producer and writer. He describes how he leverages his networks to connect people who’d never meet otherwise. CAREER STRATEGY
|
How to Improve Your Productivity
Distractions kill most people’s productivity. A habit to get into flow during certain times of the day that fit you has much more upside than downside. A non-intuitive hack is to record oneself work. Recording will make you feel like you are being watched and rewatching parts of the recording will reveal problems that you’d otherwise never have found. PRODUCTIVITY
|
The Missing Semester of Your CS Education
In interviews one of the non-obvious things people look for is if someone can use their tools, and is fast with the IDE. This is never covered in school and rarely a topic on the job. This free video series is on how to master the command-line, use a powerful text editor, use some exotic features of version control systems, and more. Have a look if you think you could work faster. EDUCATION, TOOLS
|
Ask HN: What agenda do you have for 1:1 meetings with your supervisor?
It is quite an important moment what to say during a salary negotiation or during a meeting with your supervisor. Within minutes you can make or break a five figure raise in recurring revenue (aka your salary). Here a discussion on that. NEGOTIATION
|
Tech salaries are risk premiums
Every family member you convince to buy an iPhone, use Gmail or subscribe to Amazon Prime is contributing some small percentage to your salary as a programmer. You want those tech mega-corps to succeed, and keep driving salaries up, even if you don’t work for one, because they’re helping to lift your salary at your firm. Super interesting thought process on factors that influence tech salaries. SALARIES, ECONOMY
|
Code Shame - Should you share your embarrassing code?
The answer is yes! If you’re getting better at what you do then you’ll always look back at old things you did or said and be ashamed. A thing that should regularly happen to you at New Year’s or even better, every quarter of the year. A nice article summing up looking at and showing old code. STRATEGY, CODING
|
Ask HN: Advice for a new & inexperienced tech lead
Books have been written only about this topic: How to transition from engineer to engineering manager. An interesting ASK HN about the important things to consider. ENGINEERING MANAGEMENT
|
Kotlin becomes the 2nd most popular language on the JVM
Kotlin is loved by developers for its conciseness and great integrability with the JVM. A report on its prevalence and how it overtook Scala. NEW LANGUAGES
|
My productivity app is a single .txt file
Interesting read on just using a .txt file and a simple process to manage ones tasks for the day. The authors shows that most tools are useless if you don’t have a process that you can repeat over years. PRODUCTIVITY
|
ASK HN: Sloppy PhD Hires
A very short thread about how people who are too long in academia are unfit to real jobs. If you have friends doing a PhD, send them this. THEORY VS PRACTICE
|
How Microservices Architecture Impacted the Culture of Software Development
A very short article on an underrated topic. Developers tend to oversee the implications on team dynamics that microservices, docker etc. brought about. Amazon’s notion of “you build, you run it" inspired that a team must own a product over its full lifetime. Microservices architecture brought about the concept of small code bases and made individuals more accountable for it. CODE, CULTURE
|
No engineer has ever sued a company because of constructive post-interview feedback. So why don't employers do it?
Real feedback on interviews is very rare. Candidates are almost neer told why they made it to the next round or why they didn’t make it. It seems like “too much work” to most firms. In this article you’ll learn why you should tell both negative and positive details to candidates and that the risks you see aren’t real. RECRUITMENT REALITY
|
|
If you found this issue useful, please tell your friends and share this link via Twitter, LinkedIn, Facebook, or WhatsApp. A snippet you can copy, adapt and paste is: Check out Iwan’s newsletter about tech, coding & careers: getrevue.co/profile/coderfit If you have questions, suggestions of content that should go into next week’s edition, please let me know about it, too! I will thank you publicly. Have a good weekstart. 🚀
|
Did you enjoy this issue?
|
|
|
|
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
|
|
8051 Zürich, Switzerland
|