The Bipolar Lisp Programmer (2007)

Post by netbioserror » Sat, Aug 12, 2023, 10:59 PM UTC

potta_coffee wrote: post #70

netbioserror wrote: post #63

I've found, as a Lisper, that the secret to being effective and valuable to a company such that you're both irreplaceable and not too much of a drag on the rest of the organization is to pick secret weapons that have slightly more overlap with the normal world than Lisp. Clojure, Nim, Elixir, and more faintly flirt with the true unbridled power of a CL environment, but primarily provide useful abstractions and some f…

What do you like about Nim? I've started playing with it and it's quite comfy but I don't know much about it's capabilities yet.

Post by kragen » Sun, Aug 13, 2023, 1:51 AM UTC

JonChesterfield wrote: post #120

jakeinspace wrote: post #36

I’m fairly annoyed with myself on my worse days for heading into embedded as a career path when Lisp (clojure mainly) is the only development process I’ve really ever felt fit my brain. I’m positive that there is a Lispy language out there (actually in existence, or the aether) that is appropriate for embedded work, but the constraints of the target make it difficult to envision. I like C and assembly because they’re…

Lisp makes a spectacular high level assembler but you may have trouble using it in a team environment. Think writing assembly but with lisp as the macro layer.

Post by capr » Sun, Aug 13, 2023, 6:41 PM UTC

conor- wrote: post #114

capr wrote: post #95

Earlier quoted context omitted.

That pretty much describes my "career" of the past 20 years. Lately it's been getting harder and harder to get _any_ job. These days it's either web dev which has reached unbearable levels of idiocracy with its endless tail-chasing web frameworks, microservices and even the platform itself (DOM/CSS), or it's million-line C++ legacy-on-arrival abstraction shitfests written by OOP-heads. It feels like there's nowhere t…

I've found that "devops" is a pretty nice niche to fall into, even with all of its warts. And that means devops as in literally a developer who can also provision/manage infra and operations and not just a YAML jockey who gets a buzzword title. You can kind of pick your lane: dev-experience tooling, build systems, infrastructure automation, observability systems, etc. It's a nice way to break out of the rat race of b…