HN user

TurboHaskal

1,377 karma

Yet another hacker not posting under his real name.

Primarily working on infrastructure, internal tooling, and distributed systems.

As a programmer, I happen to enjoy programming languages. Especially those that come with their own graphical development environments and allow for exploratory programming. Some examples are Factor, J, Common Lisp (LispWorks), Dyalog APL, and Smalltalk (Squeak).

I don't care about religious wars such as dynamic vs. static or OOP vs. FP. I care about programming as a function of safety, performance, and expressiveness.

I am currently playing with iForth, SPARK, and Gerbil Scheme.

email: (format nil "~{~(~a~)~}@pm.me" '(turbo haskal))

Posts2
Comments599
View on HN

I have worked at several places where SRE meant different things:

- A virtual, first responder team on call rotation for all the services because developers didn't want to be on call for their own stuff.

- Another name for a platform engineering / DevOps team.

- A team who built nothing, maintained nothing and were not paged for anything. They just collected metrics, built dashboards and spread the gospel of SRE with a big focus on form over function. IME they were annoying to work with, frequently missed the point specially when it came to stateful workloads and were ultimately just an incident factory.

Vibe engineering 10 months ago

You say this because you are on HN, very senior and/or living in a bubble.

In the vast majority of programming jobs out there you are not paid to solve problems: you are told very clearly what to do, how to do it and what technology you have to use for the job.

People don't hire analysts they hire "Java programmers".

Maybe this is just me and my experiences but when I encounter people in the wild that seem dull I often assume they just have fringe interests that are kinda problematic to share with regular people they haven't built rapport with yet.

Like they're probably into something weird or niche that doesn't translate well in casual conversation so they just keep it surface level until they figure out if you're their type of person.

Yeah I don't get it either. Lisp is perfectly fine for this task although probably makes less sense now that Julia is a thing.

Reminder that before Python was used for data science, people used things like BioPerl and PDL and that didn't stop people from working on pandas and the like.

Also let people have fun.

Simpler Backoff 1 year ago

I am afraid it is a serious argument.

If you ever feel the need to write code like that lookup table, you are working on the wrong place and you have a hiring problem.

I have found that my consumption of rock is mostly tied to my cortisol levels.

To some degree, one could say that rock / metal is a degeneration of Bach's music (and that's what makes it great).

Standing desks, split keyboards, photos of outdoor adventures... I see these everywhere. Is this the modern developer's midlife crisis at 40?

In my experience, it used to be 60% former sysadmins that didn't know how to code or approach problems from a software engineering perspective, and 40% SWE who liked doing platform stuff.

Now it's actually 80:20 due to software engineers becoming frustrated and disillusioned with the current state of things. Not only due to specialization and the push towards tool standardization (you don't get to build many custom components because we k8s all the things so most of the time you're just writing yaml/hcl), but because working with regular sysadmins gets extremely frustrating.