lunatechian (lunatech-ian)

From https://charity.wtf/2026/01/19/bring-back-ops-pride-xpost/

What’s wrong with operations? Ops is not a synonym for toil; it literally means “get shit done as efficiently as possible”. Every function has an operational component at scale: business ops, marketing ops, sales ops, product ops, design ops and everything else I could think of to search for, and so far as I can tell, none of them are treated with anything like the disrespect, dismissal and outright contempt that software engineering

"You can see that our real problem is another thing entirely. The machines only do figuring for us in a few minutes that eventually we could do for our own selves. They’re our servants, tools. Not some sort of gods in a temple which we go and pray to. Not oracles who can see into the future for us. They don’t see into the future. They only make statistical predictions—not prophecies. There’s a big difference there, but Reinhart doesn’t understand it. Reinhart and his kind have made such things as the SRB machines into gods. But I have no gods. At least, not any I can see."

— The Variable Man, by Philip K. Dick

I am in love with the book Higher-Order Perl, especially the technique in the Chapter 2: Dispatch Tables.

Today morning I came across this piece of writing - Does GPL still matter?. The whole article is based on a few anecdotes from CEOs and marketing droids. They have gotten quite a few points wrong in the article.

GPL is a developer friendly license. The basic premise of the GPL is that the user should not subtract from the freedom he gets when redistributing software. GPL is not restrictive. It merely insists that whoever takes from the common pool must contribute back to the pool.

I would like to point to these 2 articles in support of GPL -

• GPL-Virus Or Vaccine
• Why I (A/L)GPL

I attended the Hackers and Founders meetup yesterday. It was a high energy meetup and I liked it. When I walked in, I was already 2 hours late but there were still quite a few people around. I walked in, took a name tag and tried to "merge in". Merging was easy - the folks were friendly and did not mind if you joined the discussion.

Some observations

• I did not have a good answer for "what are you working on right now" . This made me realize that from a technology perspective, I have not worked on anything interesting for some time now. I have tinkered with a few things in the past 6 months (man!), but have not really done a deep dive on any of them.
• There was a focus on programming language in the group. I am not sure if the choice of a programming language is really a big deal when creating a webapp. Rails, PHP, Python, Perl, Java - all have a good web framework. One of the arguments was that it would be difficult to organize PHP code in a coherent manner. In my opinion, that is a matter of discipline instead of language.
• I did not find people thinking of totally different ideas. Or maybe, the folks were not telling those ideas . The ideas floated around ads, community, social networking, websites etc.
• I am not a unique case when it comes to the case of creating a startup. A few folks there had a regular job and were planning on side projects.

I am using a Mac now, and this blog post is brought to you by the same php and lisp scripts that I was using on my linux box. Cheers!

Have you read the man malloc page recently? Did you notice this section there

Recent versions of Linux libc (later than 5.4.23) and GNU libc (2.x) include a malloc implementation which is tunable via environment variables. When MALLOC_CHECK_ is set, a special (less efficient) implementation is used which is designed to be tolerant against simple errors, such as double calls of free() with the same argument, or overruns of a single byte (off-by-one bugs). Not all such errors can be protected against, however, and memory leaks can result. If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored; if set to 1, a diagnostic is printed on stderr; if set to 2, abort() is called immediately. This can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down.

So, you can do export MALLOC_CHECK_=1 and malloc will print debugging messages to the stderr.