@kobi_ca@zivce_@gitconnected Exchange Java by COBOL, and you know the real reason why that's the case in certain industries. It doesn't mean good news for such companies. He said he started work in 2021 and talks about "experienced" developers while assuming that knowing only Java is enough.
Why Experienced Developers Still Use JIT and JVM ift.tt/fV2KIqT
3 reasons why JIT is still relevant, and makes your builds better, even though we have AOT
Continue reading on Level Up Coding »
Wrapped up another week at my async software engineering gig.
I had zero meetings this week. I didn’t have any last week, or the week before. Come to think of it, I've only had 3 meetings in 2022. 🧘
@curtiseinsmann Multiple articles which I've combined later. Haven't really pushed it in every article I wrote. But I mention it from time to time in related topics.
Last week's launch gave me signals that I have a good product, which has demand, and is worth talking about.
March will be for marketing. I picked up Seth Godin's book to help.
I’ll be posting on:
- Reddit
- Hacker News
- Product Hunt
I'm unfamiliar with them — advice welcome!
I launched my first ever video course on Wednesday. I'm incredibly grateful to all of you who helped spread the word.
Yesterday, Master the Code Review passed $10K in revenue.
I built this for my past self, and I hope developers everywhere find it helpful. 🧑💻
Exactly 1 month ago, I started posting on LinkedIn ~4 times a week.
My email list for interest in Master the Code Review has nearly tripled in size. From 258 subscribers to 738. A 186% increase. 🤯
My "following" size was less than 1/10th of my Twitter.
@curtiseinsmann@TAbrodi I would always choose code review over pair/mob programming. With good conventions, code reviews can do wonders. When you don't have good code reviews you will naturally go to sync processes.
@TAbrodi In the context of code reviews,
Async > Sync
Async enables developers to move the needle on other tasks.
It also allows the reviewer to get into focus and flow. Reviewing is hard — it takes time, and deep individual focus.
Comment writing also forces clarity of thought.
The past 48 hours were overwhelming.
I've never sold anything before. I made Master the Code Review available for pre-order, and didn't know whether I'd make a single sale.
There have been 99 sales, totaling $1,980.
It's a small win, and motivation to finish the project! 💪
Every line of code is a line that can break.
When I was at Amazon, I knew this Principal software engineer. Their code stats for a whole year:
🟥 10 lines removed
🟩 2 lines added
Legendary.
6 years ago I could barely ship code at AWS. My Pull Requests got 50+ comments, and took 7+ reviews.
I went on to ship 550 PRs to production. In my last year at AWS, I shipped 90% of them in 1 review.
I'll soon launch Master the Code Review, to help developers do the same. 🏔
The major problem in hiring in the tech industry is that people confuse academics with practical learning. The hiring process is long, painful and confusing. It is very difficult to understand how someone can be a good fit for the job.
@curtiseinsmann `Buuut why did you change this test a lot (moved all strings to constants), we need to merge this PR fast.` - not so happy Friday for those who think like this.