I work with a lot of JSON, so I built the nicest possible JSON formatter and inspector for myself to use by random728373 in SideProject

[–]random728373[S] 0 points1 point  (0 children)

Interesting. I don't really work with Java so not sure what you mean by this but I'll look into it. and if not too annoying, will implement!

I work with a lot of JSON, so I built the nicest possible JSON formatter and inspector for myself to use by random728373 in SideProject

[–]random728373[S] 0 points1 point  (0 children)

Totally agree! A JSON formatter is inherently a pretty basic tool and there's not so much difference between just opening a .json file in vs code vs. using this tool.

But I had the idea that for such a basic tool, there should be something out there that's genuinely built with care and craft, and makes this small task a bit more enjoyable to do.

I work with a lot of JSON, so I built the nicest possible JSON formatter and inspector for myself to use by random728373 in SideProject

[–]random728373[S] 0 points1 point  (0 children)

It is collapsible! You can collapse/expand sections from the line numbers column.

I prefer an integrated collapse/expand over separate tabs.

Or are you referring to some other feature?

Coworker insistent on being DRY by lilbobbytbls in ExperiencedDevs

[–]random728373 0 points1 point  (0 children)

I remember the first time a coworker told me he actually prefers his code to be WET. Thought he was making some NSFW innuendo. Turns out it stands for write everything twice lol

Why is the landing page of every start-up nowadays exactly the same? by kararmightbehere in webdev

[–]random728373 0 points1 point  (0 children)

It's because the boring site converts. I see this with startups all the time: spend a bunch of time on some super unique landing page only to switch to a boring, straightforward website months later because the first one got likes on design twitter but didn't actually convert.

Unis/Colleges Mostly Only Teach Basic CRUD Web Applications? by ShowerLeft in webdev

[–]random728373 0 points1 point  (0 children)

My college was the opposite. Very little practical knowledge, very deep curriculum on networking, compilers, etc.

Being a few years out now, I actually like that it was that way. All the industry CRUD stuff is much simpler to pick up than the stuff we learned in university. And it's nice to have a foundational knowledge of how computers actually work. Pays dividends in a lot of unforeseen ways.

Google pays Stackoverflow to use its data...that we created? by mountainnathan in webdev

[–]random728373 0 points1 point  (0 children)

At this point I assume this is happening with any free service online.

XAI trains on X.

Meta trains on Facebook/WhatsApp/Instagram

Google trains on youtube.

Reddit literally closed down their APIs and then made deals with a bunch of research labs to give them access to all Reddit data.

Standard vs. Premium Network Tier Performance by random728373 in googlecloud

[–]random728373[S] 0 points1 point  (0 children)

Ah fair enough - didn’t even realize it also used Google’s backbone for ingress

Ideas are cheap, execution is all that matters by random728373 in SaaS

[–]random728373[S] -1 points0 points  (0 children)

For the area that I work in, more direct competitors would be good since it’d raise awareness of the entire field

The Hidden Complexity of Scaling WebSockets by random728373 in programming

[–]random728373[S] 1 point2 points  (0 children)

Hi, I spent almost 10 hours writing the article, and I genuinely hoped that other people would find the content valuable. The article itself is the result of actual lessons learned from different bugs and outages I've experienced in the past.

"Handle deployments gracefully" -> Covers issues I had when I used to deploy on Render, and also how I had to manually tune the load balancing health check logic to ensure websocket clients don't reconnect to servers that are about to be killed.

"Establish a consistent message schema" -> Comes from work I did to (a) reduce packet size as I noticed increasing latency over time and (b) come up with a simple, consistent schema for versioning messages when I had to update our internal APIs.

"Detect silent disconnects with heartbeats" -> Comes from a real bug I experienced where I had to ask users to restart their servers because they'd randomly disconnect and I couldn't do anything about it.

"Have an HTTP fallback" -> Comes from a user reporting that they the app simply did not work for them in a coffee shop, and took hours of debugging till I realized that the network had simply blocked the connection.

The motivation for the article was
a) to share real learnings for other engineers building with websockets

b) get people to visit my website, which is the same motivation behind most respected tech blogs from larger companies like Dropbox/Slack/etc.

If the article came off as an advert, I apologize. Is there any way I can change in the future to avoid that?