maverickmeerkat

To understand what service objects you need - start from business logic first. It’s very convenient to start from “big picture” overview.

This is how I will use Data class to return multiple values from a method:

Today in Postgres Is All You Need: a poor man's job queue that prevents concurrent workers from processing the same jobs.

Brutal & simple 🙂💪

Yeah. Just shared how it feels for me ;)

I will write tests that will cover code in make_second_letter_upcase, pick_letter & replace_letter, calling only public method - make_second_letter_upcase. Testing replace_letter & pick_letter separately is useless & weird.

Testing private methods is an anti-pattern for me. If developer trying to test private method - means that he can’t find conditions to test class from the public perspective. He just don’t understand how the class works or this private method with its logic is not needed & this code never executes.

Cover for Agile Web Development with Rails 8

Now in beta: pragprog.com/titles/rails...

a man stands in a field of tall grass with his arms outstretched ALT: a man stands in a field of tall grass with his arms outstretched

Celebrate freedom!

One of the hardest thing in development is to explain to PMs that eliminating tech debt is equally important as new business feature 🤕

Same. Found this site couple of weeks ago. Very useful! 🔥