Since this was such a huge problem on Twitter recently, I thought I'd make a similar announcement here on the Fediverse.
I'm just going to put this out there loud and clear right now.
If you are the kind of person who thinks that Dennis Ritchie is a somehow GOD, who can do no wrong, who has made no mistakes ever, including wrt your beloved C programming language, BLOCK ME NOW.
Hey fediverse bot authors, this is for you.
Instead of having a bot that blindly follows someone, then having a pinned toot or description that reads, "DM me "unfollow" if you don't want me to follow you any more", how about you do something sensible like looking at a user's profile and discovering whether or not they have #nobot in it first?
Because if you write bots that don't respect #nobot, you're no better than a spammer.
re: hot programming take Show more
@dankwraith Ideally, I would see the Software Engineering role as closely aligning with what I described above. The SE would be the person accountable for making sure that all PII is stored securely and that the software meets any HIPPAA, PCI, CAN-SPAM, ADA any any other domain-specific legal requirements. That best security practices are being followed and sound architectural practices implemented.
Negligent failures of the software would be the SE's responsibility. The SE can't point a figure elsewhere. If a JR logs plaintext passwords to disk it's the SE's fault for not catching it. If the product team decides to implement something evil it's the SE's fault for approving it.
In practice the roles where my title was Software Engineer was the furthest from this ideal. In those situations teams practices big-business style enterprise crap where product teams and architects put together atomic Jira tickets to assign out to whoever was available that sprint (implement a method on such and such class that does some math and returns a result). Responsibility was broken up and spread around so much it was impossible to really say the buck stopped on anyone's desk.
The roles where my title was rather unassuming ("Web Master," "Web Developer," "Programmer") have almost always been closer to the ideal where if the software clearly did something unethical, it was clearly and entirely my fault.
LISP was a vast improvement on every programming language that has followed it
I put the Debian 10 RC on my main workstation, and — knock on wood — it's been rock solid so far. I'm incredibly happy with it. The only major modification I've done has been replacing Gnome with i3wm.
Believe it or not, after 26 years of constant Linux use, this is my first time running Debian. It's a great first impression. If you're on the Debian team, please let me buy you a beer, won't you?
Zero cost abstractions, and what persuades other developers to use our abstractions: https://boats.gitlab.io/blog/post/zero-cost-abstractions/
IPv4 addresses are now so valuable that people are committing fraud to obtain them! http://www.circleid.com/posts/20190514_735k_fraudulently_obtained_ip_addresses_have_been_revoked/
people sometimes ask 'why GNU? Why free software?'
because it was only 29 years ago that people could be thrown in jail for most of their life for sharing the source code to the operating system they used, for what was basically an academic discussion of how it functioned. It would be another ~1-3 years before GNU/free versions of BSD(eg FreeBSD) were available/free and worked at all. That was what life in a proprietary world was like. That is what Microsoft would bring us back to.
Today I learned that the reason we mostly encode [CARRIAGE RETURN + LINE FEED] and not [LINE FEED + CARRIAGE RETURN] has to do with teletype machines (these were typewriters hooked up to computers that supported input and output). Because CR is moving the print head about 8 inches right-to-left, and LF is scrolling the paper down ~1/4", LF took less time. If you sent CR/LF to certain models of teletype it could do the LF *during* the CR, saving a little time.
I had spent all my life enamored by the myths of mermaids and sought every avenue I could to prove they were real.
They had to be real, the world and the tales made no sense otherwise.
It couldn't simply have been the fancies of lonely sailors unable to differentiate maiden from dugong.
Then one day my persistence paid off - my vessel was almost capsized as she climbed aboard.
At first I was confused by what I saw.
I block bots unconditionally; nothing personal. #nobot
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!