DEV Community: Rami James

Meet Doodlescan

Rami James — Tue, 24 Mar 2026 20:59:53 +0000

Every blockchain explorer I've used answers one question: did the transaction succeed? And they answer it with a decoded function signature and a table of raw values. No execution context, no way to see how that function connects to the rest of the contract.

We built Doodlescan to fix that. When you look up a transaction, it renders the called function inside a visual flow graph of the full contract. You can trace the execution path, see the guards and modifiers, the events it emits, the internal calls it makes. The function stops being an isolated signature and becomes a window into the contract's actual behavior.

The gas breakdown is visual too. You see the gas used vs. the limit as a bar, the price in Gwei, the fee in the native token, and the percentage consumed. When you combine that with the contract graph, you start to see why certain transactions cost more: storage writes, loops over dynamic arrays, mapping reads in access control checks. All visible in the graph.

It covers Ethereum, Base, Arbitrum, BNB Chain, and Polygon. Search by tx hash, contract address, wallet address, or ENS name. No account required.

https://doodledapp.com/feed/meet-doodlescan-see-what-every-transaction-actually-does

If you're not a developer, have you still ever wanted to create a smart contract?

Rami James — Sat, 14 Mar 2026 03:43:51 +0000

I've been a crypto developer for about 10 years, so I don't think I can answer this question to myself anymore. and most of my social circle is developers as well so it's kind of the same thing.

I'm trying to figure out if (or what anecdotal percentage of) non-developers have any desire to create smart contracts. Or rather, just the desire to create non-template crypto projects.

(Full transparency: this is related to something I'm building, but I don't want to promote it here because I'm really just looking to have a discussion)

Have you ever wanted to create a crypto project but felt like you couldn't because of the skill gap?

We sandbox every build. Here is what we learned.

Rami James — Mon, 23 Feb 2026 14:44:48 +0000

We sandbox every build at Doodledapp. Here's why it matters.
When you compile a smart contract in our visual builder and import a package like OpenZeppelin, that code runs on our servers. NPM packages (the building blocks of most javascript-based software) can execute code during installation.

Link: https://doodledapp.com/feed/we-sandbox-every-build-here-is-what-we-learned

In web3, attackers have exploited this repeatedly by compromising popular libraries used by hundreds of thousands of developers and draining user funds.

We couldn't just trust the packages our users import. So we built Doodledapp so that every build runs in its own isolated container, completely cut off from the rest of our infrastructure.

It's fast enough to feel instant and secure enough to treat every dependency as potentially hostile.

The trade-offs, the architecture decisions, the surprises along the way, it's all in our latest build-in-public post.

WebGL shaders with Three.js in Nuxt

Rami James — Wed, 21 Jan 2026 07:22:13 +0000

As we rethink what engagement and interactivity mean in digital products, technologies like WebGL, Three.js, and modern frameworks such as Nuxt are enabling entirely new classes of user experiences right in the browser.

Read the full exploration here: WebGL shaders with Three.js in Nuxt

In my recent write‑up, WebGL shaders with Three.js in Nuxt, I explored how GPU‑accelerated graphics and shader programming can be leveraged inside a Nuxt project to produce subtle, dynamic visual effects that elevate interface design beyond the ordinary. By executing custom fragment and vertex shaders on the GPU, we can craft organic and immersive visual backgrounds without compromising performance and, importantly, do it in a way that degrades gracefully for broader device support.

Libraries like Three.js bring 3D graphics to the web by abstracting low‑level WebGL details into a flexible JavaScript API, enabling everything from animated scenes to advanced shading techniques. This capability has transformed how designers and developers think about the “canvas” of the web. As we push forward, the intersection of WebGL, GPU computing, and framework‑driven application architecture presents an exciting frontier. Whether subtle background shaders that react to input or full 3D worlds rendered in real time, these technologies empower us to build richer, more expressive interfaces that feel alive.

If your goal is to innovate on the web rather than replicate the past, integrating GPU‑level graphics into your stack is no longer a niche, it’s a differentiator!

No More Meetings

Rami James — Wed, 21 May 2025 09:44:58 +0000

No more meetings.

👇 Join the resistance:
https://www.miserablyemployed.com/products/no-more-meetings

Not one more sync, not one more “quick check-in,” not one more hour of pretending to take notes while slowly losing the will to live.

We used to build things. Now we schedule things.
We used to do the work. Now we just talk about it.

"No More Meetings" is a t-shirt for anyone who’s been booked into oblivion and is one Outlook invite away from starting a commune in the woods.

Wear it to your next standup. Or don’t — skip it entirely. That’s the dream.

MeetingsThatShouldntExist #CorporateSatire #RemoteLife #MiserablyEmployed #CalendarFatigue #LetMeWork

The Development Process

Rami James — Mon, 19 May 2025 10:23:02 +0000

They call it “The Development Process.”

👇 Join the broken pipeline: https://www.miserablyemployed.com/products/the-development-process

You code sober.
You push drunk.
You debug hungover.
And you release out of pure, unfiltered spite.

It’s not agile. It’s not clean.

But it gets deployed — eventually — usually around 4:59PM on a Friday.
"The Development Process" is a t-shirt for the devs who’ve seen too much, fixed what should never have existed, and learned to navigate Jira like a war map.

Wear it to your next retro. Or your next resignation.

I'm the CTO now

Rami James — Tue, 13 May 2025 16:32:26 +0000

🧨 Read the full original rant from Miserably Employed:

Let me tell you a little story about unintentional leadership in tech.

Everyone quit.
The designers. The PMs. The guy who only ever talked about his standing desk.

So now… I’m the CTO.

Not because I earned it. Not because I wanted it.
But because I was too tired to leave.
What Leadership Actually Looks Like

Let me paint a picture for you:

The CEO is still slinging “quick ideas” like pancakes at a bad diner.
The investors want “roadmap clarity,” even though we’re actively sinking.
The interns? Logging into Figma every morning like it means something.

The app is duct-taped together with half-dead microservices and a Redis instance that’s been sending me weird alerts since 2021. No one’s fixed billing in months. Someone set the deploy password to “12345” and then left the company.

I deploy on Fridays. Because nothing matters.
Climbing the Corporate Ladder (From Below)

I didn’t climb to the top.
I clawed my way through the smoking wreckage of a startup with a half-finished deployment script in one hand and a Slack notification in the other.

I’ve inherited a haunted codebase.
A backlog that’s a cry for help.
A wiki that hasn’t been updated since launch day.

I answer customer support tickets.
I merge PRs I don’t understand.
I manage AI interns who hallucinate half their reports.

But I’m here. I’m still showing up. And I guess that makes me “leadership” now.
Burnout as a Business Model

Call it burnout. Call it commitment. Call it unpaid therapy.

Whatever this is, it’s not “the dream.”

I’m not a visionary. I’m not agile. I’m not optimizing anything.

I’m just the last developer standing—and apparently, that means I’m in charge.
TL;DR

Startups fail.
People leave.
The only thing that stays is the broken code and whoever’s too exhausted to run.

And sometimes, that person becomes the CTO.

Welcome to the worst promotion of your life.

Everyone quit. Now I’m the CTO. I deploy on Fridays, manage ghost interns, and answer to a CEO who still thinks we have a “roadmap.” It’s not a promotion—it’s a punishment. https://www.miserablyemployed.com/blogs/news/im-the-cto-now

Rami James — Tue, 13 May 2025 16:30:03 +0000

Have you ever accidentally created mass panic in your team's Slack? A new article by MiserablyEmployed just dropped "9 Ways to Spread Panic in Slack" https://www.miserablyemployed.com/blogs/news/9-ways-to-spread-panic-in-slack

Rami James — Sat, 10 May 2025 06:43:56 +0000

https://www.miserablyemployed.com/blogs/news/how-to-get-fired-from-a-job-you-hate

Rami James — Fri, 09 May 2025 08:30:22 +0000

That could have been an email.

Rami James — Fri, 25 Apr 2025 09:34:21 +0000

That could have been an email.

But instead it was a 45-minute slideshow with graphs no one understood.

You showed up. You nodded. You questioned the very concept of time. And when it was over, you left with the same amount of information you started with—except now you're 46% more dead inside.

This shirt says what your polite, tight-lipped smile couldn’t: This. Was. Unnecessary.

Made from ultra-soft cotton to cushion the crushing weight of wasted hours. Ideal for open offices, Zoom fatigue, and quietly judging calendar invites with 12+ attendees.

Because efficiency died so that synergy could live.

https://www.miserablyemployed.com/shop/p/that-could-have-been-an-email

Reading Documentation Effectively

Rami James — Thu, 13 Feb 2025 09:01:23 +0000

I guess that I wanted to prompt a discussion on how people should read documentation effectively. It's a skill in itself and something that took me a long time to really figure out how to do.

How do you read docs?
How much of the docs do you actually read?
Do you have a set process?
What makes for a frustrating reading experience?
What are the best docs that you've come across?

I put down my thoughts on this here