Top all-time · #19515
Szymon Krajewski
Personal blog · szymonkrajewski.plprogramming
Szymon Krajewski's personal blog at szymonkrajewski.pl covers programming. Since 2019, 4 different Hacker News readers have linked it 7 times. It is still writing: the last post was on 2026-10-01, and you can follow it by feed.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for its software and web development writing, including the early-return post. The commenters link it as a source, and one calls the early-return article great.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
About tinkering with code, tools, and ideas.
Most-linked posts?
- /why-should-you-return-early/2 people · 2 mentions · first linked 2021-02-19
What Hacker News says?
https://szymonkrajewski.pl I write mostly about software and web development but I also share tips and my thoughts on other topics. I've been writing since 2017. Most popular: * https://szymonkrajewski.pl/why-should-you-return-early/ * https://szymonkrajewski.pl/why-you-should-use-array-function... But I don't think they are the best, rather needed.
Comment linking /why-you-should-use-array-functions-instead-of-basic-loops/
on “Ask HN: What is your blog and why should I read it?”Submitted The practical difference between “findBy” and “getBy” in repositories (OOP) as a story · 1 points
HN discussionWith Live Share you see their text selections, but not mouse movements. (except inside the Draw.io integration [0], then you see a remote mouse that is drawn by the extension itself). It's a bit like Google Docs or Etherpad, but for code. Also: other editors could implement the same protocol perhaps, it would be cool. [0] https://szymonkrajewski.pl/drawio-real-time-collaboration-in... here it says it doesn't show th…
Comment linking /drawio-real-time-collaboration-in-vscode/
on “Tuple: Pair Programming Tool for macOS”I totally agree. I love Swift's guard let. It makes early returning [1] easy: guard let value = optvalue else { return // optvalue is none } There has been several proposals [2][3] to fix it in Rust but they don't seem to go anywhere. I'm using this in my own code now to unwrap or return (it looks stupid): let value = if let Some(value) = optvalue { value } else { // optvalue is none return; }; [1] https://szymonkra…
Comment linking /why-should-you-return-early/
on “Where Everything Went Wrong: Error Handling and Error Messages in Rust (2020)”Negative, this keeps things consistent and clean. Here's a great article https://szymonkrajewski.pl/why-should-you-return-early/
Comment linking /why-should-you-return-early/
on “Ask HN: Do you follow the positive or negative pattern when programming?”