CodeAhoy

codeahoy.com · Personal blog · on HN since 2016

CodeAhoy publishes software engineering articles on rewrites, technical debt, abstractions, and Linux tools explained visually.

What HN saysHN commenters link it for the visual htop explainer and for its piece on failed rewrites, which one commenter uses to argue for incremental rewrites.
21HN people shared it
2linked it in comments
40stories submitted
1.0Kstory points
5 years agolast shared
2016people per year2026

Most-shared posts

  1. 1
    YAGNI, Cargo Cult and Overengineering
    4 people · 19 points · first shared 2017 · 1 comments on HN
  2. 2
    Htop Explained Visually
    3 people · 349 points · first shared 2017 · 40 comments on HN
  3. 3
  4. 4
    Technical Debt Is Soul-Crushing
    3 people · 10 points · first shared 2020 · 1 comments on HN
  5. 5
  6. 6
    Good Abstractions Have Fewer Leaks
    2 people · 6 points · first shared 2016 · discussion on HN
  7. 7
    Do Software Developers Normally Code on Weekends?
    2 people · 5 points · first shared 2019 · discussion on HN
  8. 8
    Experienced Programmers Use Google Frequently
    1 people · 291 points · first shared 2016 · 174 comments on HN
  9. 9
    Write Less Code
    1 people · 8 points · first shared 2016 · discussion on HN
  10. 10
    Mistakes at Work Are Not Sins
    1 people · 6 points · first shared 2016 · 1 comments on HN
  11. 11
    Git Pull vs. Git Fetch (and Stashing)
    1 people · 5 points · first shared 2016 · discussion on HN
  12. 12
    Serverless Architectures: Let's Ditch the Servers?
    1 people · 5 points · first shared 2016 · discussion on HN
  13. 13
  14. 14
    The Complete Guide to Feature Flags
    1 people · 5 points · first shared 2021 · discussion on HN
  15. 15
    Effective Coding Standards
    1 people · 5 points · first shared 2016 · 3 comments on HN

What HN people wrote when they linked it

zython · 2018-01-26
If anyone else likes linux tools explained visually heres one for htop: https://codeahoy.com/2017/01/20/hhtop-explained-visually/
TheCoelacanth · 2017-12-04
If you can't do your rewrite in an incremental way, it is almost guaranteed to be a failure[1][2]. If you can make it two weeks without making any visible progress, you project is probably not on track for success. Granted, if your management thinks that they can get an entire multi-month project broken down into stories in advance, they have their heads up their asses. [1] https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-p… [2] https://codeahoy.com/2016/04/21/when-to-rewrite-from-scratch-autopsy-o…

Keyboard shortcuts

/Search
j kNext / previous blog
EnterOpen selected blog
vVisit the blog site
fFollow / unfollow
lSwitch grid / list view
dSwitch dark mode
g hHome
g pTop posts
g tTopics
g fFollowing
g lLiked
g yHistory
g qFAQ
EscBack / close