Codeminer42 Blog

blog.codeminer42.com · Company blog · on HN since 2016

Codeminer42, a Brazilian software company, writes about Ruby, Rails, React, front-end patterns, and other engineering topics.

What HN saysHN links it for its Rails and React posts; one commenter singles out a post on working with the Lean 4 language as fun.
16HN people shared it
2linked it in comments
41stories submitted
471story points
8 months agolast shared
2016people per year2026

Most-shared posts

  1. 1
  2. 2
    React 19 almost made the internet slower
    1 people · 202 points · first shared 2024 · 284 comments on HN
  3. 3
    Git Workflow Basics
    1 people · 187 points · first shared 2016 · 75 comments on HN
  4. 4
    Ruby on Rails: The Open-Source Blueprint
    1 people · 20 points · first shared 2025 · 14 comments on HN
  5. 5
    What's New in Ruby 3.4
    1 people · 6 points · first shared 2024 · 1 comments on HN
  6. 6
    What's New in Ruby 4.0
    1 people · 3 points · first shared 2025 · discussion on HN
  7. 7
  8. 8
    Common patterns in scalable front end applications
    1 people · 3 points · first shared 2018 · discussion on HN
  9. 9
    Crystal by Numbers: Kemal vs. Sinatra / Rails
    1 people · 3 points · first shared 2017 · 1 comments on HN
  10. 10
    Good communication in software development teams
    1 people · 2 points · first shared 2016 · discussion on HN
  11. 11
    Working Effectively with a Headless CMS in React
    1 people · 2 points · first shared 2024 · discussion on HN
  12. 12
    Third-party cookies are phasing out, now what?
    1 people · 2 points · first shared 2024 · discussion on HN
  13. 13
  14. 14
    Git Basics: Adding more changes to your last commit
    1 people · 2 points · first shared 2016 · discussion on HN
  15. 15

What HN people wrote when they linked it

alwillis · 2023-01-17
> Should I group by behaviour type — put all the margins and padding in one place, all the font stuff in another? How does that jive with grouping in a different dimension: by element hierarchy. All the buttons stuff in one file. All the headings stuff in another. I've been where you are. All I can say is Inverted Triangle CSS (ITCSS) [1] solves the issues you're talking about. It's so obvious once you get it—it's one of those "why didn't I think of this" kind of thing. You write your code in specificity order. It sounds odd at first but it makes total sense and eliminates so many of the "issues" people complain about. It makes the cascade your friend and not your foe. [1]: https://blog.codeminer42.com/how-to-organize-your-styles-with-itcss-37…

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