Nick | OneThingWell.dev

30+ years in software development, mostly posting on topics related to: #tech #programming #webdev #foss #linux #devops #infosec #privacy

[Nick | OneThingWell.dev @onethingwelldev]

A bit about me: I started playing with programming languages when I was a kid in the early 90s.

I'm still on a journey to learn as many different ways to build (and break) things as possible. [1/2]

#techtwitter #buildinpublic #100daysofcode

[Nick | OneThingWell.dev @onethingwelldev]

Does this thing still work?

[Nick | OneThingWell.dev @onethingwelldev]

@CSDevAr I'm just passing by through the circus, but nice to see you too, Charly :)

[Nick | OneThingWell.dev @onethingwelldev]

@ggwhiting Hey Gareth, I'm rarely visiting this awful site anymore... you're still active here?

[Nick | OneThingWell.dev @onethingwelldev]

@SrihariVernekar There's definitely less idiots than here, but it's simple to use. Bluesky currently requires an invitation, Mastodon generally doesn't.

[Nick | OneThingWell.dev @onethingwelldev]

@SrihariVernekar Like Twitter, but more sane.

[Nick | OneThingWell.dev @onethingwelldev]

@DonDubya200 followed!

[Nick | OneThingWell.dev @onethingwelldev]

@dgut_ At this point, Twitter is a lost cause, and the sooner we accept that, the better.

[Nick | OneThingWell.dev @onethingwelldev]

@EduSchwarzkopf I don't know much about German, but "Sorry" somehow doesn't look like it belongs there :)

[Nick | OneThingWell.dev @onethingwelldev]

@charafmrah Yeah, I have projects in nim where I was fetching the data from the index in memory, rendering and returning the response in <1ms. Just "SELECT 1" from MySQL would take way more than that :)

[Nick | OneThingWell.dev @onethingwelldev]

@charafmrah and keep hot data in memory. For freelancing, at this point I'm okay with pretty much anything I come across :)

[Nick | OneThingWell.dev @onethingwelldev]

@charafmrah Compression was a separate issue, MySQL scaling was a much bigger issue - it wasn't only sluggish, the site was completely dead most of the time, and users have starting to give up on it.

For my own projects, I tend to go with something more low-level (like lmdb) [1/2]

[Nick | OneThingWell.dev @onethingwelldev]

@charafmrah Yeah, it's a tricky position. Ideally, if you're working on something that has a potential for getting big, you'd think about scaling right from the start and implement adequate architecture. On the other hand, there's a good chance that the project will fail and it won't matter.

[Nick | OneThingWell.dev @onethingwelldev]

@charafmrah a foundamentaly different approach than you'd use with a typical MySQL setup.

[Nick | OneThingWell.dev @onethingwelldev]

@charafmrah Yes, I understand. But it's also important to understand that scaling MySQL is a nightmare. You mentioned YouTube... I don't know if you remember the early days, but it wasn't pretty - not being able to scale MySQL almost killed it. Sharding requires [1/2]

[Nick | OneThingWell.dev @onethingwelldev]

@ggwhiting :)

This seems to be the cause of the bug: https://t.co/IqJWJGYgx3

[Nick | OneThingWell.dev @onethingwelldev]

@indefiniteloops Yeah, or leave all this crap behind a become a Buddhist monk.

[Nick | OneThingWell.dev @onethingwelldev]

@indefiniteloops Yes, Twitter told me that programming is dead, prompt engineering is all the rage now :)

[Nick | OneThingWell.dev @onethingwelldev]

@Quasicodo Yes, "cesspool of digital narcissism" doesn't even begin to describe post-Elon's Twitter :)

[Nick | OneThingWell.dev @onethingwelldev]

@TomR4vn Yeah, it needed some convincing to tell the truth, but we got there :)