rozenmd

shops you actually want to work at don't have "mandatory conditions", they have criteria that match an ideal candidate.

if you think you can do the job, track down the hiring manager and convince them.

The job has never been about "writing code". You're there to solve problems for the business.

I'd reach out to people you've worked with before and ask if they need help.

Writing unique, useful content that only you could have written.

Cloudflare free is the business model: https://blog.cloudflare.com/cloudflares-commitment-to-free/

Not _quite_ in this case, since the free plan improves everyone's experience: https://blog.cloudflare.com/cloudflares-commitment-to-free/

I used to keep all of OnlineOrNot's timeseries data entirely in a hot postgres db with the rest of the relational data.

Used to take a few seconds to get a week's uptime data and do some useful analysis.

Since moving to Clickhouse I think I can grab a full year's data in around 200ms (probably less if I try optimising it). Still completely blows my mind everyday.

Something doesn't add up between the pricing and the core pinning for me (or maybe I misunderstood):

Say you're using a m8i.large (2 vCPUs, $0.043/hr on spot pricing). Is the article saying you dedicate a whole physical core to one browser or am I totally misunderstanding here? If so, are you taking a loss on every browser hour?

Surprisingly rare occurrence: https://stackoverflow.onlineornot.com/

I worked on a project that used yarn from the early days all the way up to v3, it's slow as hell, but it works. They also have the supply chain protections.

Eventually we snapped and migrated to pnpm. Installs (both in CI and on local dev machines) are significantly faster. Turned out to be about a day's work to migrate with an LLM's help.

Common knowledge: https://en.wikipedia.org/wiki/Lock-up_period

the best part is Downdetector is inaccurate as hell - if AWS is genuinely down, folks get curious and search other providers, causing Downdetector to mark them as down too

Charging by the hour was one of the worst things for my career (was just starting out). Never realised at the time that I was subconsciously doing a slower job and not trying to make it faster or really improve until I left.

You can already ship single executables, my product's CLI is a Node single executable application

I don't touch AI for writing.

"Googlebook, because lets face it, your parents are only watching YouTube anyway"

Do you happen to live in Perth/Australia? https://www.cloudflarestatus.com/incidents/qs4k7rpkhspd

Several newer alternatives that outperform it on Node, like Hono

This is incorrect.

You preface with PUBLIC_ to expose them in client side code.

Still OnlineOrNot (https://onlineornot.com/) - I've been working on adding more and more configurability to the browser checks feature.

More recently, I've made it so you can drop your existing playwright test suites into the code editor, and it'll Just Work.

A whole bunch more work to do around that, but I think letting folks drop code in makes more sense than continuously updating the UI.

A CV that tells me what you did, and what benefit it had to your employer.

I'm only impressed by side projects if they had users and/or MRR - something serious that proves you worked on it long enough to have something to show for your efforts

At the same time I wouldn't skip a candidate for not having a portfolio - a full time job is enough

This is the perfect use of cloudflare containers. Rare, bursty workloads that fit around regular use of Workers.

I use them to generate thumbnails when uploading large photo files for my personal flickr clone, not even noticeable in billing.

that makes sense, it's not 1.0 yet

apparently too many outbound requests is enough to get on their radar

I've been celebrating five years of working on OnlineOrNot (https://onlineornot.com/) by adding more features for teams that build software:

- 2FA, PassKey, and password-based login for folks that hate magic links

- Moved my entire API from GraphQL to REST so I can fully dogfood the API I offer

- Added an audit log as standard on all plans

- Built a terraform provider (https://github.com/OnlineOrNot/terraform-provider-onlineorno...), and a way to download existing config into terraform files

- Started iterating on a CLI (https://github.com/OnlineOrNot/onlineornot)

I'd be terrified to run anything other than a classic web server on Hetzner, have heard too many stories of them arbitrarily terminating workloads they didn't understand.

Have you seen the price of RAM recently?

You can't get a hackable watch for a fraction of the price, though.

I'd pay more for being able to fumble about in the codebase and add exactly what I want.

Most engineers I know are now picking off backlog items and tech debt //TODOs dating back several years.

Things that I had labelled "too hard, pain in the ass" I'm now finishing in half an hour or so with proper tests and everything.

It's an exciting time to be a product engineer IMO.

Yeah I've been seeing a lot of 500 errors myself, latency seems to have spiked too: https://github.onlineornot.com/

Yep!

Planning on writing one for OnlineOrNot's 5th launch birthday (Feb 25)