← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 70
  1. This is episode #07 of the Ruby Stained Glass Notes, a pop-up newsletter in which I write about the process of building a stained glass panel celebrating Ruby.

  2. This is episode #06 of the Ruby Stained Glass Notes, a pop-up newsletter in which I write about the process of building a stained glass panel celebrating Ruby.

  3. In the 5th episode of the Ruby Stained Glass Notes, we talk about cutting glass and where impostor syndrome come from.

  4. This is episode #04 of the Ruby Stained Glass Notes, a pop-up newsletter in which I write about the process of building a stained glass panel celebrating Ruby.

  5. This is episode #03 of the Ruby Stained Glass Notes, a pop-up newsletter in which I write about the process of building a stained glass panel celebrating Ruby.

  6. This is episode #02 of the Ruby Stained Glass Notes, a pop-up newsletter in which I write about the process of building a stained-glass panel celebrating Ruby.

  7. This is episode #01 of the Ruby Stained Glass Notes, a pop-up newsletter in which I write about the process of building a stained-glass panel celebrating Ruby.

  8. After talking with Jeremy Smith and Jess Brown on the IndieRails podcast about stained glass and how I transitioned to programming in Ruby, I’ve had this crazy idea that I could tie the two together in a weird project.

  9. Last week, I spent an extended weekend in Rimini, Italy, for the first edition of Rubycon where I gave a lightning talk connecting my reconversion story with the current trend of throwing junior developers under the bus for the sake of (AI) productivity.

  10. I joined Jeremy Smith and Jess Brown on the IndieRails podcast to talk about how I managed the transition from stained-glass master to freelance software engineer.

  11. A small mistake sent me on an overly long investigation into Minitest hooks, and how Rails integrates with these.

  12. Reflecting on 2025

    Time to recap a good year.

  13. While I already covered the basics of `Minitest::Spec`, I forgot to discuss a few aspects of the spec flavor.

  14. What is Minitest::Spec?

    In my previous post, I talked a lot about how Minitest comes in various syntax flavors.

  15. Marketing Haikus

    Just a list of haikus, mostly written when I was working (and being bored out of my wits) in marketing.

  16. I have a confession to make: I have never used Minitest in the seven years I've been a professional programmer.

  17. For years, people around me have been telling me to learn new programming languages—that I shouldn’t corner myself with Ruby (and Rails).

  18. A while ago, I needed to add some view-related instance methods to a model.

  19. One of RSpec's strengths is the legibility of its behavior-based DSL.

  20. When working on features, I strive to preserve my flow, which means, that after a few hours, I'll have a bunch of untracked files waiting for me in git.

  21. Today, I want to share a different type of post.

  22. Interacting with third-party APIs is common practice in applications.

  23. Where I share a badly designed piece of code, think about what process I can use to reveal its flaws, and how to make it better.

  24. Add extra documentation to your columns attributes with this one weird trick.

  25. Delegated types are a modelization pattern introduced in Rails in 2020.

  26. Pick a standard and move on

    Why would you spend your cognitive capacity on useless choices?

  27. For years, code would fall into two categories: easy (good!)

  28. Growing old as a programmer

    I’ll be turning 40 this year, and I’ve started to wonder about my professional life in the next two decades.

  29. A few months ago, I had to write a Rails micro-service that synchronizes data between two versions of an application.

  30. As I'm reaching the end of this recruiting cycle, I wanted to reflect on the recruiting processes I've completed.

  31. Something happened to me last week I didn't expect: I enjoyed working my way through algorithms.

  32. Today, I would like to try something different.

  33. For years, I've worked without thinking much about feature specifications.

  34. Today, I want to share how to test your Rails models with RSpec.

  35. A few weeks back, the creator of Ruby on Rails wrote a pamphlet rejoicing on - what appears to him as - the waning days of DEI's dominance.

  36. Changing careers is a long, often-overlooked process.

  37. Feature flags (or feature toggles) are a neat way to hide in-progress features from your users.

  38. Classes depend on each other all the time.

  39. No matter how thorough your test coverage is, you can't test everything.

  40. You're about to upgrade your application to the newest version of Ruby on Rails.

  41. Working on large features can be tricky.

  42. In this second part of my introduction to RSpec, I want to focus on the syntax.

  43. When you start programming, it's not easy to know what to test, how to test, and why should you test?

  44. Always serving someone

    It's easy to tell yourself it's not your job to provide a great service to your users.

  45. Time to level up your debugging game with frames, adding breakpoints on the fly, and some handy shortcuts.

  46. Active Record Associations are a great feature of Rails.

  47. For the last eighteen months, I've spent my time trying to understand bits of code I'd never seen before.

  48. This week, I did my first live stream on Twitch and it didn't turn out so well (to say the least).

  49. Let's look at how we can update parts of our app's pages with asynchronous HTTP requests.

  50. Like most new developers, I started as a puts developer.