Tech Watch & Dev

Everyone talks about moving to the cloud, but is it always the right choice?

For a small business with stable workloads (website, email, file storage, backups, internal apps), does buying a server once and running it for 5–7 years make more financial sense than paying cloud bills every month?

I'm also thinking from a business perspective. If you were starting a business today with a small budget, what service would you offer that brings recurring monthly income?

I'd love to hear real experiences from people who run infrastructure or do businesses from home network not just theory or marketing.

It would have functionally no use and would never be spoken. I still say we need a name for it.

Claude Code Opus 5 and Fable 5 both fail at basic things when creating UI. Of course it looks generic AF. But it also has blatant problems like each button styled a bit differently, completely half-assing most URL work and stuff clearly clipped through the container or the viewport.

To be fair AI works damn well for backend, systems, cryptography, backend-in-the-fromtend work. And I am using the Chrome MCP to let it auto-debug in the browser etc and (only a couple) other skills.

Are your results different? Has anyone cracked it and do you have any advice?

I built WebAIM — a fully browser-based recreation of AOL Instant Messenger, the chat app that defined the internet for a whole generation.

Sign in with a screen name, build your buddy list, blast someone with a "lol brb," set a cryptic away message quoting your favorite band, pick a buddy icon, join a chat room, and actually talk to real people in real time — all with the authentic Windows 98 look, classic door-knock sounds, and every bit of the nostalgia.

What's under the hood:
- Real-time messaging powered by Firebase
- Buddy lists, groups & online presence
- Away messages with auto-reply (and the classic %n, %d, %t variables)
- Buddy icons & editable profiles
- Group chat rooms
- The actual AIM sounds
- Full Windows 98 desktop UI — taskbar, desktop icons, start menu, the works

I just can't recollect when I stopped doing that.

TL;DR: Is there already a good framework/starter-kit for designing good maintainable frontend/backend monorepos? I'm not talking about bundlers like turborepo or NX, neither I'm talking about t3-stack or better-t-stack, I'm talking more of a very strict paradigm to design typescript frontend/backend monorepos.

I am currently slowly migrating a vibe-coded prototype to an actual production-ready product and I'm noticing how I'm slowly starting to hate the freedom TS/JS gives you, the fact that you can shape your codebase how you wish, the first refactoring I did was migrating all those scattered small sloppy ts files to domain services/sub-services, providing strong hiearchy (Java/C# like), but then noticed that I wasn't leveraging monorepo's features the fullest, so I had to modularize everything, but here I don't know what to do anymore, I don't think I was the only one facing this issue, and I can't migrate to another language 'cause we just can't afford it. The architecture I've thought of was to divide domains in packages and make packages have a strict structure both folder-wise and code-wise:

@acme/foo/
├── app/
│   ├── services/
│   │   └── foo/
│   │       ├── index.ts
│   │       └── types.ts
│   └── routers/
│       └── index.ts
├── data/
│   ├── models/
│   │   └── index.ts
│   └── index.ts
└── web/
    ├── components/
    │   ├── Foo.svelte
    │   └── Bar.svelte
    └── index.ts

But I feel I'm reinventing something someone must have already figured out, but I don't know where to search anymore...

Once I got past a couple of machines, SSH-ing into each to run

docker/kubectl/systemctl stopped scaling. Curious how others handle

it. one tool, a stitched-together stack, or just tmux and grit?

Where does your approach start to hurt?

I feel like I spend more time evaluating libraries than actually integrating them.

Is the hardest part:

• Finding good options?
• Comparing similar libraries?
• Figuring out which one is actively maintained?
• Understanding the API?
• Something else?

Such as accecibility with axe devtools, FCP with datadog, error tracking, etc

Hi everyone,

I’m currently an SDET (exp 1 year, total exp 2 years) at a Tier 1 tech company and I’m planning my move into a platform engineer role. I love building tools and want to be closer to product development and feature ownership.

For those who have successfully made this pivot:

Did you find it easier to transfer internally or interview elsewhere?

How did you bridge the gap in System Design if your daily work was focused on automation frameworks?

What was the single most helpful thing you did to prove you were ready?

Appreciate any insights or "traps" to avoid!