Now the news site and admin console is all in Next.js and slow and no feed.
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.
What sort of companies are those were receptionists have access to tools beyond their role? and why are people approaching the receptionists asking for data queries?
Like having to run a script on that data when your machine doesn't have the permissions to run arbitrary software without permission from the IT team
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
By scanning the records in other doctors, competent ones, could see other patients. For me, I was ok with doing this job even though it is officially inappropriate.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)
At many companies (especially old, stodgy companies) this gap is artificial. The day you get asked "hey, I've got some data .... and I need ..." and you successfully solve the person's problem, is the day you become the office's live-in software engineer. That person you helped will be back, and they will bring friends.
The rest after that is just job title shuffling.
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.
Dammit I really wish Plan9 had taken off. It isn’t perfect but it does a much, much better job of helping me run my applications in ways that I want.
If anyone doesn’t already know, one method of Plan9 remote access is to “cpu” into a remote machine which has the hardware you need. Your local filesystems go with you, and your environment on the remote machine consists of your local filesystems mounted to the remote machine, but only for you, and all applications you run in this context execute on the cpu of the remote machine and have access to the remote machines hardware, but your local filesystems. Imagine SSHing into a remote machine and your entire environment goes with you, development tools and all. That’s what Plan9 does for you.
So if I “cpu” into a machine without ffmpeg, but with a GPU and I run ffmpeg, not only will it work, but I can tell ffmpeg to use a hardware encoder with a simple command line flag, and it’ll work.