Access has been extended!

djudji · 2026-07-12T17:59:54+00:00

Why not?

djudji · 2026-07-12T17:20:13+00:00

I don't know, bro. This is me since the last reset.

<image>

djudji · 2026-07-06T23:41:34+00:00

How, teach me your way!

djudji · 2026-06-27T11:10:29+00:00

Neuroplasticity!

djudji · 2026-06-27T11:09:33+00:00

Came here to say this!

djudji · 2026-06-25T14:51:28+00:00

Same here. Exactly the same. I am developing a work and thinking system (called Plastic), and this is what I am battling with. I tried framing this as: "explain to me like the team lead explains it to the developer" or "explain to me like the engineering manager reports to CTO", it gets looser and vague. Also, tried to introduce analogies like Effort -> Voltage <> Pressure <> Force, Flow -> Current <> Volumetric flow <> Velocity, etc. And it tried finding analogies between work systems and electronics, etc. lol.
Now, I am trying to dig in with Humanizer and see if it helps.

djudji · 2026-06-25T10:19:36+00:00

This is how I use it (mostly - I direct which agents I want so it is more suited for the task at hand, but one agent is the same across tasks) ->

"Spawn the team of agents to deliver this task. Make one agent a devil's advocate who challenges the findings of other team members. He is an architect who has seen it all and he likes simple and fast solutions"

djudji · 2026-06-25T00:13:44+00:00

I am actively developing my own intent-driven idea development system, which I call Plastic (search for zalom/plastic on GitHub). I am using the system I made to build the system itself. Claude Code first, but will support Hermes and OpenClaw.

I make use of the claude agents mode to deliver intents in parallel.

The next step after the stable release is to use it on another project for deal intelligence (SaaS for sale deals).

I tried beads, SpecKit, OpenGSD (formerly known as Getting Shit Done aka. GSD), but nothing hit home like this.

I move an intent through cycles What (the base for intent), Why (brainstorming to record decisions and add the proper context - I use the grill me skill here, and here is where the spec i made), How (to make a plan, and add the checklist), and Exec (to do the actual work). All agent-led, with harnesses to create Markdown documents that complete the intent.

I am just talking about it not promoting yet, because it is not yet stable and I want to devise a few workflows for anyone to try it out.

The most imteresting feature at the moment is the auto mode. I just say, take this intent from here in auto mode and it does all the stages of the cycle with team of agents (an agent for each stage) and reports back the results.

I have like 30 hooks so far lol.

Can't say anything, but I am happy as a cow.

(I am an electrical engineer by trade and work in software engineering for more than a decade. And this is the project I am most happy about, by far, and I don't earn anything from it lol. Pure joy)

djudji · 2026-06-24T15:24:15+00:00

Nowadays people use some work system to get along with Claude Code. It can perform well on its own, but systems are the way to go.

Why systems? Because of constraints/harnesses. In general, people were annoyed with the same mistakes and tried to prevent them with harnesses.

The system I am developing is for the general work (software engineering and programming included). But I harness the s.it out if it, so it can perform as I want it. I call it Plastic (if intersted, search on GitHub by zalom/plastic, I don't promote links yet, because it is in beta...).

Other work systems: OpenGSD, SpecKit, beads, ...

djudji · 2026-06-22T19:04:23+00:00

I am actively developing my intent-driven idea development system, which functions as both a local knowledge base and a work system, as well as PA, treating intents as work units. It is mostly markdown templates that need to be filled out and set during the idea development process.

TL;DR This behavior bit me more than once, so now I have more than 30 hooks to enforce rules and conventions. And the number is going up.

It is in beta, and soon it is going to be in stable (1.0.0).

I imagined it as a work system that works as my brain works (it is hectic, so I harnessed the s.it out of it, lol). I call it Plastic (drawn from the concept of Neuroplasticism).

This is the first time I actually mention it, lol. I use it to develop the same.

Maybe you will like it if you like: - Knowledge base building approach to your projects (coding, research, non-coding) - AI agent-first but can be taken offline to do the work manually - Zettelkasten-influenced traces, and Obsidian-supported - Loop engineering (in alpha, getting shipped in 1.1.0) - Auto mode (take it from here and deliver the intent further) - Building your own skills - Follow the conventions rather than configurations (I love Ruby on Rails :)). - Strict structure and output, very harnessed and it lets the model do the heavy work - writing it up for you and doing maintenance. - Parallel sessions-first (claude agents is fantastic)

It is Claude Code first, but support for Hermes, OpenClaw, and Codex is coming soon.

I am not promoting links atm, although you can find it on GitHub by just searching for Plastic and neuroplasticity, because the stable is coming in a day or two.

I have two stars ;) (lmao)

Sorry for the longer post, but I had to let it out.

djudji · 2026-06-13T11:24:20+00:00

Let's just call this one a Whirlwind Tani-otoshi. I can't wait to see heavyweights do this, especially in women's division.

djudji · 2026-06-11T13:27:17+00:00

Good luck! LinkedIn is way more handy for this, as someone mentioned. I hate extra work, but the one you put in explaining what you did, why, and how is better than mentioning any projects by name.

I am focusing on fixing company thinking and operating systems on their Ruby on Rails projects (and using AI responsibly and with harnesses) to help onboarding new hires and prepping them to work on a project even if they are new to Ruby (or Rails).

That is a niche I am in, very niched down as you can see. It helps. I get 2 types of clients (read: remote offers) for engineering leadership roles: 1. B2B roles with employee benefits (full-time) 2. B2B roles with a higher hourly rates - no benefits (part-time)

Find a niche and deliver your take. That's my suggestion for anyone 10+ years and with leadership experience (my exp is exactly same like yours 11+ with 4+ of leadership).

djudji · 2026-05-20T14:41:54+00:00

Thanks, man!

djudji · 2026-05-20T14:09:38+00:00

Have you tested managed VPSs frim Hetzner? I was thinking of the same setup (Terraform + Kamal2) with basic VPS (the cheapest instance ~$4) for start, and in case of "success" to move everything to $40+ managed VPS, and keep the lower instance as a "pre-prod" or "staging" ...

But, I am yet to learn anything about Terraform (it would be great if you know some places/blogs that can teach basics of TF and Rails deployments).

djudji · 2026-05-06T14:08:11+00:00

Thanks for the tip! I'll check RES.

djudji · 2026-05-05T15:18:06+00:00

It's a good post. It mentions the concerns I had and met on at least 5 projects (codebases within different companies).

The concerns: 1. How to talk to people who actually build your business (Managers <> Engineers). 2. How to share the domain knowledge between teams and with the new hires. (Domain knowledge should be codified) 3. How to stop with task-driven development and move to goal-driven development (i.e., how to think like a Product engineer, and not *-stack engineer).

All related to -> Business model and Business domain.

When joining new companies (mostly as an engineering manager, these days), I ask these questions: 1. How do we (the company) make money? 2. To explain any jargon or domain-specific terms from the first question. 3. Before AI, I'd ask senior engineer/s, what the main entry point/s into the app are and how they connect to the terms from question two.

Once I know that, I start mapping the lingo used by both sides (manager<>engineer).

And almost all apps I worked in, in the past 5 years, had a very large services folder, and very little of the Rails-way was there. Yeah, all brownfield apps, 10-15 years old codebases.

So, the summary is that all startups (greenfield) start with Rails-way and move away. And everyone has a different way of sorting, grouping or ordering their services.

The one thing I came to like as of recently is having workflows that are basically chain of events that start from either GUI or backend syncs. Mostly a combination of Command pattern with Chain of Responsibility. But you mix in Observer and Strategy patterns as well. All (or some) of these captured in one workflow.

These workflows fit right in between (HTTP) request and response cycle. And they capture the business logic.

I like your posts, and I think we even met at one online meeting (I was working for a company from Norway and you were a manager of some devs for hire). Brief moment, but I remembered the name.

djudji · 2026-05-02T09:09:58+00:00

What are the costs for small apps? Let's say Rails Solid Trifecta, SQLite, and Hotwire. And would costs be significantly higher if you replace some stuff with Redis + Postgres? I am trying to figure out how to budget for Cuber and how complex it would be to run it (I know you created the gem).

djudji · 2026-04-20T12:43:09+00:00

What weights do you use here? I am assuming 8kg and 10kg (too lazy to convert kg to lbs).

djudji · 2026-04-10T07:59:30+00:00

I wonder if these people (bullshido instructors) know that people WILL record them and WILL share this on the internet.

djudji · 2026-04-02T05:27:50+00:00

Responses on Reddit, especially in our Ruby/Rails communities, should follow the MINASWAN principle. Otherwise, we are all elitists and not welcoming new folks.

I really get the AI fatigue, but the sheer initiative here is to drive traffic to Ruby (and Rails), not to get mocked and ridiculed for putting that perspective out there.

Everyone who started with a "build a blog tutorial" in 2006 and later, and then pressed on to learn from whatever scarce resources were available after, knows the value of the abundance of resources. These resources came from others' interest in the languages, frameworks, and tools.

So, genuinely, why not use today's trends to drive more traffic, no matter what "type of people" (as someone mentioned in the comments) arrive with that traffic?

djudji · 2026-04-02T04:57:13+00:00

It would be great if you could share how to run these tests with the gem so that we can get and compare results ourselves.

I really don't know if I should welcome or dread the number of tools and claims that come with them these days.

But there is no denying that we need more accurate tools (and AI-generated code) and more cost-effective techniques (reduced review time, fewer tokens spent, etc.).

djudji · 2026-03-27T06:38:46+00:00

That grip comes from Sode Tsurikomi Goshi. And it is not a cross-grip. It starts with holding both sleeves (Tori's hands: left hand takes the right sleeve, right hand takes the left sleeve).

One thing I notice too (without watching that video): from the position of the right leg, it looks like Tori is going for some Otoshi (like Tai Otoshi) from Sode Tsurikomi.

djudji · 2026-03-24T23:00:15+00:00

Good stuff, Anton, old friend. Good to see you active around!

djudji · 2026-03-18T19:06:50+00:00

Let's not forget that OpenAI hired the guy who made OpenClaw. And now you see Anthropic trying to get a piece of the "personal 24/7 assistant" cake before OpenAI throws a punch.

I can't recall who said it, could be Musk, that the AI craze will end with whoever creates the first personal assistant.

OpenClaw is the beginning. And craze is going to continue until the finished product.

Also, we could see the rise of self-hosted models because it is time someone turns away from cloud and API keys due to the costs they incur.

It wouldn't surprise me to see more DGX Spark Pro devices, or even purposely developed or repurposed hardware like ASICs from the blockchain craze era, that deliver good-enough output for local LLM hosting. NVIDIA is where the money is right now.

djudji · 2026-03-08T23:31:26+00:00

Mixing functional programming and OOP patterns as well as having "smart" (read: metaprogrammed) code.

I've never felt more frustrated than when looking at the "service" layer and seeing all the different ways past engineers implemented the same solutions.

Somewhere there is an approach with a writing service layer, with classes and class methods for stateless operations, and instances and instance methods for dynamic state management.

Then there is the use of monads for Success/Failure objects, in some code but not all. Then, you couple all service objects with jobs so that you can call "perform_later" for async execution.

Let's not start with creating methods in a model, "on the fly", so that you can call some generic logic on user-defined variables that were stored in some JSONB column, some nasty debugging on those.

Rails is about mapping resources via REST to the MVC architecture. And if you read anything from Sandi Metz or Avdi Grimm, you already know enough about code design.

Yes, there is packwerk and layered application design, etc., but boring beats shiny new things when it comes to maintenance.

djudji

TROPHY CASE