In which Facebook basically admits their platform plays to our worst instincts https://www.politico.com/news/2020/09/26/facebook-conservatives-2020-421146
Someone last me week asked—not rudely, but with a genuine desire to understand—why people still write code and not computers.
I think we do ourselves a disservice by calling ourselves "coders." There's a lot more to what we do than write code. Writing code is the result of a lot of planning—planning that might happen more or less unconsciously, but happens regardless. And these parts are less easily automated.
Facebook was purposely engineered for growth, engagement, and addiction. Am I surprised? Not in the least.
And if you want simplicity in programming, then I assert the following:
Static > Dynamic
Compiled > Interpreted
Simula-, C++, Java-style OO is a failure
Reflection should be used sparingly
That was really just a set up for this Dennis Ritchie quote: “A language that doesn’t have everything is actually easier to program in than some that do.”
The Stack Overflow Antipattern https://riggraz.dev/stack-overflow-antipattern.html
Mozilla has lost its way, making the web browser game a virtual monopoly. Google wins.
If anyone needs me, I’ll be hanging out on Gopher and IRC. Might also check out Gemini.
Now that I’m trying to work with the API, this seems like a dumb question. Checked exceptions are too burdensome.
Changelog was kind enough to feature my recent post on semantic versioning:
Incidentally, I had been reading nobs(1) as "knobs," but I understand now that it should be pronounced "no-b-s" (bs for backspace, but one could think of more creative expansions).
Adding a second DoT provider to my forward zone seems to have resolved things:
Software Engineer. Adjunct Professor. Christian, husband, and father. Opinions are my own. Aphorisms are experimental. he/him
A private Mastodon instance