Robert Pankowecki
@pankowecki
Followers
2K
Following
52K
Media
822
Statuses
13K
Full stack developer, software architect, working mostly with Rails and React.js #Rails
Wrocław
Joined November 2011
P.S. Join us at wroclove.rb as a speaker - CFP is now open here
papercall.io
The [wroclove.rb](https://wrocloverb.com) conference is the place for Ruby professionals to confront ideas in a friendly atmosphere and with mutual respect. We encourage our speakers to cover a bit...
0
4
5
Articles like this are what Internet was made for. Great content and form. https://t.co/lQwQJP83e6
0
0
0
There are some things that AI already fantastic with. I am doing project X about changing Y to Z, what should I be mindful about, do change management analysis in POLDAT model. Bang, 100 details to think about.
0
0
0
Entire Reddit thread of similar problems. Rewrite Driven Development https://t.co/mGOvvOZfrY
reddit.com
Explore this post and more from the ExperiencedDevs community
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service
1
0
7
@dkubb @andrzejkrzywda @arkency My vision is for Mutant to become a cornerstone for Ruby teams, human or AI-driven, who care about bulletproof code.
1
2
2
We’ve used Mutant at @arkency for over a decade. Now we’re joining forces with @_m_b_j_ to bring it to more Rubyists and push it into the future of validating both human and AI-generated code. Ruby deserves tools like this. ❤️ https://t.co/ongucgRe8n
Mutant story/news time, thread:
1
7
30
This isn't a Ruby vs. Go problem. It's an "we hired 50 engineers so let's split everything apart" problem. Here's what happens: Company grows fast. Leadership comes from Big Tech. They bring their playbook. Split the app into pieces. One piece per team. Everybody owns
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service
42
127
1K
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service
230
354
5K
Unfinished migration from Rails to Go/Kotlin/TypeScript microservices - a very typical situation nowadays. Merging microservices back to Rails is often the right thing to do. Adding more network calls rarely solves a problem with a big Rails app.
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh. They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service
5
13
184
CFP for #wrocloverb 2026 is already open! ⏲️ We aim for ~30 min talk 🗣️ First-time speakers are more than welcome! 🗓️ We are waiting for your submissions until January 13th https://t.co/eCF3NnwzI7
papercall.io
The [wroclove.rb](https://wrocloverb.com) conference is the place for Ruby professionals to confront ideas in a friendly atmosphere and with mutual respect. We encourage our speakers to cover a bit...
0
8
8
Agents should store their todo lists using a DAG rather than a linear list of tasks. They can still topo sort it so it appears linear to the user, but if tasks are modelled based on their dependencies and dependents, it would make parallelization easier in the future.
0
1
4
When was the last time you saw "No space left on device"?
0
0
0
Karen Jex was recently at Euroko with a talk about Postgres Partitioning Best Practices. She just published a blog on the same topic with a great partitioning example case and it is packed with excellent advice. https://t.co/iXX3DfKir0
0
5
24
Save the date! @wrocloverb is back on April 17–19, 2026 💎 We’ve got big plans to make this edition unforgettable. Stay tuned for updates - and see you in Wrocław!
0
6
23
Here is what you can expect
0
0
1
0
1
5
I am on the opposite opinion, it does excellent job, but I always point in the prompt to existing files for it to get our preferred structure, setup and conventions.
It’s fascinating how absolutely terrible agents are at writing tests. Claude sucks at writing test harnesses and tests and I don’t really get why. The quality of tests in the data set surely must be higher than what it produces.
0
0
2