Location: Manteca, CA, USA Remote: Yes (required) Willing to relocate: No Technologies: Common Lisp, Emacs Lisp, Java, Python, SQL, AWS, Azure, Kubernetes, Terraform, PostgreSQL, GitHub Actions Résumé/CV: https://sinistercode.com/public/donnie/resume Email: macnod [at] gmail [dot] com

Looking for a remote senior software engineering role or DevOps that is still engineering.

Remote senior software engineer, 20+ years. Last year was DevOps (Azure, AWS, Kubernetes, Terraform); I still write as much code as ever.

I write programs that write programs. Data UI is a compiler: a 57-line model becomes PostgreSQL, REST, React, row-level RBAC, and a Kubernetes+TLS deploy, versus roughly 20,000 lines of hand-built Java. https://data-ui.com

Common Lisp is the working language, not a hobby. The environment is Emacs with several AIs from different services in one instance: they see each other's buffers, cooperate with each other, especially when it comes to planning, and can edit the live Lisp they run in. The harness sits on gptel-agent. The rest is mine: define-gptel-agent, paren-balance checks, bash timeouts. Agents never stage or commit; I review unstaged diffs and commit myself.

https://sinistercode.com/public/donnie https://github.com/macnod

I haven't used Windows in years. But I used it for a long, long time at work. And I became more proficient with Windows after I learned Linux.

You don't need Linux for anything, but learning it can make you a better programmer.

According to this person, KWrite is better than Emacs and Emacs is a bug. In my opinion, this makes his post a little less credible. The rules that he suggests we all learn for how to use tabs and spaces in a file are helpful, but only when you're forced to use tabs. Otherwise, using spaces is always easier when you have to share your code with people that are not required to use KWrite.

I personally use kwrite. That doesn't mean it's "better" than emacs, just that I prefer it. Editor use is an indiviual choice, and people are more productive when using the editor of their choice.

Similarly, people are more productive when using the indentation style of their choice. I like 3 or 4 spaces of indenting, and I find using 8 spaces makes the code hard to read. Other people have different preferences. It seems to me that the best way to accomodate everyone on a multiple-developer project is to require that code is run through a formatting utility before being checked in, and to allow people to use similar utilities to format it when checking it out and editting it.

Out of curiosity, I wrote a simple non-optimized quicksort function in Common Lisp (SBCL) and timed a 180,000-element sort at 567ms, about half as much as the Java version. I'm sure that could be improved greatly with better coding and type hints.

Here's the code http://donnieknows.com/blog/sbcl-fast

I think in extremes:

If you're a computer and software user, OSX is the way to go.

If you're a hacker, you can code in more than 10 programming languages, and you've been writing code for more than 10 years, then you'll be way better off with Ubuntu.

If you're somewhere in between, stick with OSX.

Forget about Windows for now. But don't be surprised if they come out with something truly wonderful some day.

No degree. I've been programming professionally for 20+ years. Usually better off than my peers salary-wise (since the beginning). Generally regarded as the best amongst the programmers I know personally (which is a bad thing, in my view). Started several companies. Most failed. One sold. Have had a 9-5 job for the last 3 years (telecommuting from home). Title: Senior Programmer Analyst. Actual Work: developing new products (programming).