Live data from Hacker News

Ask HN: Share your favorite software blog posts of 2023

news.ycombinator.com

11–20 of 86 posts

Re: Ask HN: Share your favorite software blog posts of 2023

#11

https://danluu.com/ is my all time favourite. Unfortunately hasn’t posted in 2023, but I reread old posts often.

do you have a specific post? I think entire blog would be too big to check out, just to be in line with this post

Mine is: https://danluu.com/p95-skill/

Re: Ask HN: Share your favorite software blog posts of 2023

#13
This post (The Techno-Optimist Manifesto), but in particular this section (that contains such gems as “Our enemy is anti-merit, anti-ambition, anti-striving, anti-achievement, anti-greatness”): https://a16z.com/the-techno-optimist-manifesto/#section--13

Re: Ask HN: Share your favorite software blog posts of 2023

#14
Technically not a blog, but the FIRESHIP youtube channel changed my life: https://www.youtube.com/@Fireship

A wild mix of super short videos about current software engineering topics, extremely well made, always on the edge of slapstick comedy, trashy memes, inside jokes, but still extremely densely packed with actual information. Plus, the nearly daily video series "the code report" is godlike: https://www.youtube.com/watch?v=GyllRd2E6fg&list=PL0vfts4Vzf...

Re: Ask HN: Share your favorite software blog posts of 2023

#15
Working With Discovery Trees: https://www.industriallogic.com/blog/discovery-trees/

Happened to see Paige Watson present about FaST Agile at the PhillyXP meetup group and then tried some of the concepts with my team at work to great success. We were looking for a good way to turn high-level product asks into actionable work and Discovery Trees fit the bill for us.

Re: Ask HN: Share your favorite software blog posts of 2023

#19

The Big TDD Misunderstanding https://linkedrecords.com/the-big-tdd-misunderstanding-8e22c...

My opinion on methodologies is that if it is too often misunderstood, then it is wrong.

The entire point of giving a methodology a name and writing about it is to get everyone on the same page. So if people have different ideas on what TDD is, then people should stop talking about TDD until everyone agree what is and what is not TDD.

And only after everyone agrees, one should talk about the pros and cons and assess the success of the methodology depending on the situation. "you are doing it wrong" is not helpful.

Back to the article. I think not mentioning TDD at all would make it a better article.

Re: Ask HN: Share your favorite software blog posts of 2023

#20

The Big TDD Misunderstanding https://linkedrecords.com/the-big-tdd-misunderstanding-8e22c...

The biggest missing element, in my mind, of the pro-"classicist" and anti-"mockist" view is that the practice of writing unit tests with mocking leads to refactoring your code until it works with that approach, which in turn leads to better-designed code. I don't like the emphasis of "yeah but refactoring code leads to needing to rewrite mocked tests", because if you've designed your code well, then the need to adjust an api boundary should be less frequent than the need to adjust the internal implementation details. Focusing on integration tests means you can get away with poorly designed code full of corner cases that your integration tests can't catch. Besides, "we can keep the fast feedback loop with parallel tests" really increases the demands on complicated tooling that breaks often.
Post reply on HN