qubyte

Naïvely I tried to do this by overriding a few custom properties and using filters. My site has a position: sticky nav, and filters introduce a stacking context, so things which filters apply to naturally go on top of the nav when before they went behind. A minor annoyance, but it demonstrates how introducing a dark mode isn’t as straight forward as I thought it would be.

I'll see your mid-2012 mbp and raise you a late-2010 mba. It's slow now, and the processor lacks some features I need for work (docker stuff), but otherwise it runs well enough. I'm hoping it lasts another year so it can claim a full decade of service.

My work machine on the other hand is a 2016 mbp (with touchbar and butterfly keyboard). I swear the thing is haunted from all its weirdness and glitching. Then there's the keyboard...

I got a shortcut to log when I've fed my baby, and create a reminder to let me know when he'll start to get hungry again. This way I'm not constantly checking my watch. The best part is that it works with Siri, so I can trigger it with my voice since I won't have a hand free.

It's one I hand rolled in Node. It boils down to markdown for blog entries and handlebars for templates. Not exactly in vogue, but I've found the mix (with a little hacking around) very productive. The code is at https://github.com/qubyte/qubyte-codes if you're interested. :)

Don't worry about the design. That can come later. Just get a single, well formed HTML page up there with a few words. Once you have that the design and content problems will seem less insurmountable.

I spent years agonising. I even wrote my own Node.js framework before I finally realised it was all procrastination, and put together a static site and deployed it in a few minutes. Over the years I've added features and improved the static site generator, but the design is still a bit rubbish!

Thanks for the links! I'll miss the old workflow and its syntax (allowing for parallelism), but I'm keeping an open mind.

I've been on the beta for a while, and while it was understandably limited, I really enjoy it and have done a lot with it. I'm excited about the announcement because it appears that a lot more can be done now.

However, it's not clear what happens to existing actions and workflows. Do they just stop working? Can actions still be made from a dockerfile and entrypoint script?

One good thing about ES5 code is that it is ES6 code. ES6 is essentially a superset. Why refactor it when it works already and will always be more compatible as it is?

I cut my web-teeth on CGI. I was a TA instructing physics undergrads in C (I think around 2007). I only really knew C and python myself, and was tasked with building a page which students could upload programs and results to. It was the perfect abstraction given the tools I had and my primitive understanding HTTP at the time.

It took a few yesrs to realise I was hooked, and while I don't use CGI nowadays I'm really glad I started out with it.

I read this and it struck me as irresponsible too. By all means hack your own pump, since it's your own life you're risking. Absolutely do not hack the pump of another. I'd be concerned if doing so is even legal.

Regarding webmentions, webmention.io (receiving) and webmention.app (sending) are excellent. If you prefer to manage your own like me, then you may find this glitch helpful: https://glitch.com/~lean-send-webmentions.

I've also written a complement to webmention.io which it can use as a callback hook to turn webmentions it receives into GitHub issues (great for if you use a static site generator). https://glitch.com/~webmention-io-webhook-to-github-issue

CSP interacts in a surprising way (at least it was to me) with service workers.

https://qubyte.codes/blog/content-security-policy-and-servic...

I don't think everyone must have a website, but I do think many more people would if they realised that the cost and difficulty of setting one up are much lower than they used to be.

A personal site can be about pretty much whatever you want, and look how you want it to look. It doesn't need to be a sales pitch, or on topic all the time. It doesn't need to come top in google when you search for your name. You get to decide why you're building it and who your target readers are (if any).

A few others have mentioned it, but this reminds me of shisa kanko, the pointing-and-calling system used in Japan.

https://www.atlasobscura.com/articles/pointing-and-calling-j...

Soon (it's available): diditreallyneeditsveryowndoma.in

PhD in Physics (2009, quantum optics and quantum info, both theory and experiment). After my first postdoc in Tokyo (mostly computational in C++ toward the end) I decided to move into industry and worked as a Node.js server dev for a games company there. Got married!

These days I'm back in the UK (Brighton) and enjoying the arrival of my first child. I'm still working in Node for API and unusual proxy servers, with some Rust on the side. Enthusiastic about the indieweb movement.

When I was a curious ~10 year old, yes, I too did!

I got a bit too invested in this last year. I even did a write up of one of the tasks. That year I did it all using JS since it's easy to write input parsers with it. This year I'll be doing it in Rust to stretch myself a little.

https://qubyte.codes/blog/advent-of-code-2017-day-20-task-2

I built something similar (though probably a lot less sophisticated) as an alpine based docker image. I had some issues with openssl on a Mac in the past, and this approach circumvents those.

https://hub.docker.com/r/qubyte/cert-creator/

This may depend on where you live. Down here in Brighton we've an abundance of bakeries selling excellent breads.

The "Lead and Take Charge" point is an interesting one, which I don't entirely agree with (if I'm reading it correctly).

I mentor weekly (codebar) and sometimes find myself not knowing the answer to a question. When that happens, I'm honest about my position, and then show the mentee how I go about figuring out the answer. After a couple of times I get them to suggest an approach to answering it. By doing this, I cede control. The point, after all, it to make myself redundant as a mentor!

Seems quite similar to https://github.com/kelseyhightower/nocode

I took the nuclear option and switched careers (there were other reasons too, but it was one of the big ones) from academia to software engineering. Since then I've stayed in a job no longer than 3 years and the constant need to learn may have killed it off, which seems paradoxical.

Then again, I'm also honest to a fault since the switch. Nobody can think I'm an imposter if it's obvious when I don't know stuff!

This is great! It reminds me that I need to do smaller projects with faster turnaround. They're much more fun!

In fairness, the thesis is dated 1975, and it remains a useful thought experiment due to its simplicity.

I do this when I'm walking around the house (no shoes allowed), partly because my heels eventually hurt when walking on hard surfaces with no padding, but mostly so I avoid treading on a lego brick or a type G (UK) power plug (though this is the first time I've thought about it, so these are assumptions).

I also run on the balls of my feet, but I never thought about why I might do that until I read an article about it a few years back.

New challenge: A robot to assemble a given maze as fast as possible.

It was a long time ago, so I don't remember an awful lot. He caught me off balance from the start. I remember bringing ID and asking him if he needed to see it. With a hint of an amused smile he replied "I know who you are, young man." Other than that, he just kept me chatting. It seemed perfectly natural at the time.

This guy was a retired police officer, as it happens.

The article mentions getting someone to like you unnaturally fast to divulge information.

This happened to me once. I was a character reference for a friend who needed security clearance for a position in the UK, and they sent a a guy to come and interview me. About 45 minutes later I came out of the room and quickly realised I'd been mined for information (all good, luckily for my friend). While it was happening it felt like we were having just a nice chat. Afterwards I was totally exhausted. A very strange experience.