Now the news site and admin console is all in Next.js and slow and no feed.

Moving from auto tools to Zig’s build system was a huge quality of life improvement. Most of the work since has been deleting features and tidying up the code to make it easier to reason about. I realise there may not be that much value porting C to Zig the more I work on the project. Instead I see is there’s huge value in the usual stuff: clearly defined functions, preferring stack to heap allocation, minimising global state.

But it’s still quite early days. I’m looking forward to porting the trickier network code to Zig and using its built-in testing.

[1]: https://git.olowe.co/?action=summary&path=talons

[2]: https://claws-mail.org

[3]: https://sylpheed.sraoss.jp/en/

It's a fair question. I questioned myself all the time doing the job. The couple of competent doctors couldn't see other patients as the doctors couldn't get paper records themselves. The old retiring doctors (one had a genuine diagnosis of vascular dementia) sometimes hid the paper records for themselves. Admin staff stopped bothering sorting the records properly some years back too. You needed to just know where some group of patient's records were in which cabinet. The workflow for accessing records, in the morning:

    1. study the appointment book
    2. open delivered snail mail, set aside ones for patients who had appointments that day
    3. get each patient's records, attach any new mail (real attachments with paperclips!)
    4. place them on each doctor's desks

Despite this strict paper workflow, there were 3 PCs on the front desk to be used by any admin staff at any time. No password to log in ("too slow" otherwise). The password to log in to the medical software was "1234" ("too slow" otherwise... again). The practice purchased computers only to be able to bill patients using credit/debit cards and to get rebates more quickly from the government.

> ... permissions to run arbitrary software without permission from the IT team

There was no IT team. The practice called an IT support company who billed per 10 minutes - no contracts - if the "server" didn't come back up again after a disk failed or somebody kicked the cables. The practice staff stopped calling the IT team once they saw that I could do the job myself (see my longer comment)

Every couple of days "the server" would crash. It was an old dusty Windows box under one of the admin staff's desk. I offered to move it out so they wouldn't keep accidentally kicking out the power cable or disturb the wobbly ethernet switch making it fall down off the top of it down into the corner where the mice and moths hid. I was sick of crawling down there after a while.

Once staff saw that I knew how to plug network cables back in after moving IT gear, they stopped calling in the IT company meant to be keeping all this stuff on life support. From there you hear about every tiny little problem, you get busier, learn to automate bits of your job piece by piece to keep up with the demands.

For example, a doctor complained about waiting for me to scan in pathology reports delivered by snail mail. The fax machine kept running out of toner & paper as it was also the practice's main printer. I researched and found that the pathology providers could install some software on a Windows machine which would deliver reports directly into the medical software the doctors were starting to use. That software would crash, too. How can I monitor that Windows service and have it send me an email if it goes down? What if I could get it to try to start it back up again before it sent me an email?

Eventually the dementia doctor retired as he kept falling asleep during appointments.

The other old doctor voluntarily quit when the filing cabinets containing all the paper records moved to a locked room with just a scanner and shredder.

A doctor wanted to be able to connect to the practice remotely. I learned about VPNs, but I had no idea if I could set that up using the modem/router provided by the ISP. Some family friend referred me to the IT company who took care of their email. Turned out that company were real Linux purists running all their own mail system in a datacenter. They were impressed by my proposed network diagram for the medical practice. They thought it was cool that I installed Linux on old PCs to keep using them for fun.

Instead of me hiring them for support, they just offered me a real salary job at a bit over minimum wage.

Perhaps it was the way it was written; I couldn’t believe intrigue and passion of computing could be weaved together like this. But there it was.

I did make it home eventually. Fortunately the first 2000km lift back from western Australia to the eastern states with a crystal meth addict on the run from the police didn’t end violently. A few weeks back in Sydney with family some Linux nerds found me working as a receptionist answering phones and scanning paper records in at a failing medical practice. They got me doing desktop Windows and Linux server support. I’m an official software engineer now. I guess I should print this article out to show to my kids!

SMART criteria[1] can help to get out of a rut. "Making the world a better place" is very difficult to satisfy. How many people? What is better? How much better? I don't advocate for quantising abstract ideas in general but sometimes the thought process of coming up with a number and hitting it helps to get going.

My current dayjob involves me wrangling a clunky Java system written like FizzBuzz Enterprise Edition[2]. Keeping this abomination running and getting paid for it feels soulless. Yet I genuinely believe I'm able to stick to my values.

For example, there are 3 components tightly coupled to proprietary AWS systems (AWS Lambda and Simple Queue Service). I feel this has made the world a (very slightly!) worse place; Amazon to me represents the bad side of humanity (greed, scrupulousness). Furthermore, people new to the software dev industry may never know that it's possible to implement these kinds of systems using significantly simpler, portable designs without making a deal with the devil! My goal is to refactor the system to instead use the language's built-in concurrency primitives to perform the same work.

The next person who sees the refactored work can more easily take it and run with it without needing to know anything about AWS. That person doesn't need to care either; I can always share this story with others who I don't work with. Maybe AWS does something so egregious that it's distasteful even to company executives; I can confidently say that we're not as tied to AWS as we think.

I'm not changing the entire world for all eternity. But in a way I am changing my little tiny insignificant slice of this world today in ways that I hope to inspire even just 1 other person in their own tiny insignificant slice :)

[1]: https://en.wikipedia.org/wiki/SMART_criteria [2]: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It may be worth trying to ignore the feeling of "AI taking over the field". There's so much noise around this stuff as, personally, it's very difficult to differentiate hype and utility at the moment.

For me this was an eye-opener. I kept trying to wrap my head around all these different paths and "standards" because I thought it was correct and deliberately designed. Looking back through the history this doesn't seem to be the case; I feel much better for being confused by all the different PATH conventions and strict hierarchies.

This very article loaded 2.49MB (uncompressed) over 30 requests. It's served using Next.js (it does actually load fine with JS disabled).

Ironically this is a great opportunity for the author to have made a stronger point. It could have gone beyond the abstract desire of "going back to basics" to perhaps demo reworking itself to be served using plain HTML and CSS without any big server-side frameworks.

Shocking it took them so long but, hey, it's there now.

> If this had been available in 2010, Redis scripting would have been JavaScript and not Lua.

With that in mind we can do a quick search to see how Lua is used. I found an article on Wikipedia titled "List of applications using Lua"[2]. Of course that's not an exhaustive list but it gives you a bit of an idea. Off the top of my head, the places I've personally seen Lua used:

1. modifying DNS responses in PowerDNS

2. neovim plugins

3. video game mods like Factorio

Personally I got into programming by writing shell scripts. I never studied computer science or IT. Instead it was the ability to write basic code for existing software that gave me this accidental introduction to the world of writing logic down as a set of machine-readable instructions. For me, MicroQuickJS is another one of those ways for "power users" (who may themselves be professional software developers) to extend some existing software without getting into the nitty gritty of the big bad upstream dev project.

[1]: https://news.ycombinator.com/item?id=46368706

[2]: https://en.wikipedia.org/wiki/List_of_applications_using_Lua

Think about it this way: you've spent a decade writing software.

> Does it make sense to change direction at this point?

Changing direction isn't a binary thing. You can aim, say, 4.5 degrees to the left to change your trajectory ever so slightly. This is possible because whether you're working on CRUD forms or self-driving car data analytics pipelines many principles of software engineering are the same. For example good software is usually simple, clear, and portable [1].

Specialise in an industry vertical that is not just web development. Let's use healthcare as an example. If you're doing dropdowns and modals in healthcare software - try and understand if those widgets could be easily used in other healthcare software. Why or why not? Could that same dropdown be implemented in a native app using GTK and/or WinUI? Perhaps given the type of data you're working with a dropdown isn't the best way that it could be represented. Try loading up some disease definitions into Typesense[2] and presenting a more free-form text search for particular diseases. From there you can think beyond UI widgets and think more about general problem solving.

[1]: https://en.wikipedia.org/wiki/The_Practice_of_Programming [2]: https://typesense.org

I worked on an IoT project at one of the big German car makers and it was a mess. More money than sense. They didn't really have any idea why they were putting software into stuff. Just some vague notion that some software systems needed to exist to then present its existence to the next boss up; presumably all the way up and out to investors. Discussing the actual functionality or how the product(s) would actually be experienced in the real world was essentially taboo.

There was a podcast called garbage.fm [1] with one of the hosts working for General Electric at the time it was recorded. It sounded like GE were yet another one of those incumbent companies doing "smart" Internet of Things products just because they were worried about being left behind.

[1]: https://garbage.jcs.org

Exactly. We changed from some fancy one that my boss gave me to a cheap one that you operate with an old-school (can't believe I'm saying that) infrared remote. It doesn't "think". It just works like our other reliable dumb machines - diswasher and washing machine. We don't own a regular vacuum cleaner as I just do a regular sweep with a broom when we want a thorough job done.

All other home tech gadgets friends and family have acquired live in limbo land stored in the back of the draw or on top of the cupboard, never opened or tried once but got stuck downloading some stupid app. But we can't just throw it away yet, as there's guilt around acquiring that smart tech thing in the first place even though we know there's already so much e-waste.

Not sure this counts as a fork or when it was “reworked” by OpenBSD, though.

FWIW I take issue with the tone (petty name calling, elitism) of the comments. And I disagree with the assertion if I understand the original comments correctly (that there’s some kind of technical incompetency to blame?).

Maybe I wrote my comment because I was surprised that the article was even amended at all. I dunno.

It’s messy and the Zig project are taking on a lot of challenges. Didn’t see this battle being picked but here we are!

I applaud the migration, and I sympathise with the difficulty of running open-source software projects.

Hoping Andrew is ok. The fact he withdrew his comments is a sign of humility. I guess in this context that’s more important than whether you agree or disagree with the comments.