TurboHaskal
Joined 11 years ago
Joined 11 years ago
- 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.
The proprietary implementations are also quite good.
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".
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.
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.
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.
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))