Alice laughed. "There's no use trying," she said. "One can't believe impossible things."
"I daresay you haven't had much practice," said the Queen. "When I was younger, I always did it for half an hour a day. Why, sometimes I've believed as many as six impossible things before breakfast."
I know I've commented before on how, while Clean Code has its place, there are adherents who adhere to it so literally and unthinkingly that they've constrained their careers and condemned themselves to the same silos for the rest of their professional lives.Continue Reading
As I'm building out the design and model of Scarlett (which seems dangerously likely to get renamed 'Notesmachine' at the rate I'm going), I've hit one of those architectural things that annoys me. Allow me to ruminate on the problem.
As mentioned in the previous post, the traditional organization of any notes system is that of the Forest; each Box contains notes, some of which are the roots of trees, and the rest of which are nodes of the tree leading to leaves, which are notes that have no descendant notes.
On the other hand, I have interests that are orthogonal to that design. Let's take them in order:Continue Reading
There's a difference between "What you do" and "What you really do."
An I mentioned earlier, I'm looking for work. Given that I'm not working, and doing the looking only takes half the day, I'm spending the other half of the day diving back into Rust. Those two events came together in a conversation I had today with a "career coach" in an unexpected way.
My career coach loves my elevator pitch:
I have a very broad range of experiences, but what I do comes down to this: using industry standard application servers like Django and Swagger for the back-end and familiar tools like React or Backbone for the front-end, I build user interfaces for complex business process that make them easy to understand and a pleasure to use.
If you're like me, you have more than one hard-drive full of random stuff: notes, PDF files, Epub files, ZIP and TAR files, GIT repositories of (mostly incomplete) projects, and so on and so forth. Also, if you're like me, these projects devolve into a bunch of different areas: my professional life, my artistic and creative life, my open-source footprint, my personal life like my kids and my wife, the infrastructure of my life like the current projects in home maintenance, and in my case an imperial buttload of recipes.
My Rust has gotten rusty, so to speak, so I've decided to try and write something to help me manage it. This post is mostly me rambling about what I'm going to write, gods help us all, and how I want to manage writing it.
Basically, I want a knowledge base. That's it. That's the simplest thing possible. In fact, pretty much what I want is some kind of Roam clone, but one with extra superpowers.
I'm going to use a term that doesn't exist in the real world: "egotonin." Egotonin is a mythical substance that gets used when you're exerting willpower; it is the thing that is depleted in the concept of ego depletion.
So lets talk about Knowledge Bases.Continue Reading
If you've ever looked at your
.bashrc file and wondered how the heck
it got so weirdly out of control, look no further than the slow
migration of "local changes" to the
.local folder, and the number of
language– or framework-specific environments that are now kept there.
There's much to recommend this move, not the least of which is
$HOME directory. But my biggest pet peeve was the
$PATH variable, which seemed to just grow and grow in my
file into an unreadable string. I've decided to fix that. Here's how.
I just finished one of those take-home programming assignments that companies are sending out these days in lieu of whiteboarding exercises, a process that I'm genuinely thankful for. Whiteboarding is just a way to stress someone out; it doesn't prove anything (except excessive cleverness, sometimes). We work with a fully immersive IDE (even if Emacs is still making itself difficult in that regard), we work with StackOverflow available, and we work surrounded by books, notes, and cheatsheets. We even work with our fellow workers on the other end of Slack and Zoom.
A lot of what I did was "re-learning," but it's always good to go over it again, just in case. Here's a lot of what I absorbed:Continue Reading
I’ve been hacking on a secret project that I’ve had in the works since, oh grief, the first check-in was:
<code>commit ccb93ca5f2b256babfa0f2ef9110ac0ac4019527 Author: Elf M. Sternberg <email@example.com> Date: Mon Feb 4 23:03:01 2013 -0800 Initial check-in for Scarlett.</code>
I’m going to use the word “abstraction” in two different ways, but bear with me for a moment and consider this:
1. Every startup is based on an insightful abstraction of a complex idea. 2. Every software abstraction is leaky in some critical way.
Uber is an abstraction of taxis. How do we abstract “what a taxi is” using the higher-level technologies we have now? Amazon is an abstraction of mail-order sales, which have been around since Sears pioneered them in 1897. Google is an abstraction of card catalogs and yellow pages. And so forth.
In programming, an abstraction is a higher-level description of a process or mechanism that is designed to hide some level of complexity behind a simple set of controls. The menu on a word processor hides the complexity of the software behind it. The API we use to “log in with Facebook” or “log in with Google” hides the complexity of securing your authorization across multiple websites and applications while revealing your identity to advertisers.Continue Reading