Michael Sheldon @shatteredgears@mastodon.technology
Software Dev, C/SQL, DNS
Greyhound adoption advocate
Helpful hint for the OCD #1248
If you are in the middle of the workday, no matter how boring the conference call is, do not pop off one of the keycaps from your keyb....
You just did it, didn't you?
Yes, it is disgusting, and no, you won't be able to ignore it now. So, you're going to get soap and water?
What? Well, yeah, it's pretty bad.
Yeah, I'm pretty sure that flamethrower will sanitize it.
You sure you want to do t#@$%^(*!
Language rant Show more
I've been catching up on unit tests for old code for the past few days. I really hate writing them, but watching the code coverage percentage getting closer to 100% triggers my competitive and OCD tendencies, which keeps me doing it.
But my last commit message today was "more unit, much test", which make me think it may be time for a break.
Past me didn't document a thing that should have been documented, so present me spent an hour re-figuring everything out and documenting it.
Past me is a jackass. Don't be like past me. Document your things.
But it sounds like you're editing prod.exs ? , you might want to generate a config first and edit prod.secret.exs
In my case this is how the config was generated by default.
@shatteredgears
Finally gave up and set iptables rules.
/sbin/iptables -A INPUT -p tcp -s 127.0.0.1 --dport 4000 -j ACCEPT
/sbin/iptables -A INPUT -p tcp --dport 4000 -j DROP
Not a fan of doing it that way, since it's easy to forget something set elsewhere.
Network app developers: Listening on 0.0.0.0 by default without telling the admin how to easily change it is a FRIKKING BAD IDEA!!!
Pleroma admins:
pleroma is running on *:4000 with apache proxying to it via 127.0.0.1:4000
Is there a way to configure pleroma to only listen on 127.0.0.1? Or will I need to just iptable that?
@shatteredgears Clarification. The 500 error occurs when I try to "follow from a different account" (I have multiple accounts set up in Subway Tooter). It doesn't happen if I follow from within that account's timeline. So would appear to be something specific with Subway Tooter?
So, in all, I'm finding Pleroma pretty easy to deal with.
The install wasn't horrific, and was probably more involved than most because of running CentOS/Apache rather than Debian/nginx. Part of that ended up with me running certbot in full-out manual mode. Still, I've dealt with FAR worse.
The only oddity I'm dealing with right now is attempting to follow someone from Subway Tooter results in a 500 error from my pleroma server, where doing it via the web UI works fine.
I'm working on a list of what it means to "commit responsibly." What would you change/add to this?
1. Not committing bugs or broken builds
2. Not leaving in dead code or print statements
3. Formatting code to your style specifications
4. Using meaningful variables
5. Providing documentation where necessary
6. Using descriptive commit messages
finally found the box with my RasPi
still dunno what I want to do with it lol
A good thing about working from home:
I can put together a long-cooking dinner at lunchtime, and let it cook until dinner.
A bad part about working from home:
I then smell dinner cooking all day while I'm trying to work.
I'm so hungry.....
if you expect a process to fail, and it does...
Was that a failure, or a success?
One of these days, I expect cppcheck to return a message: "Are you sure this is the right career for you?"
I really, truly, cannot wait until this whole blockchain fad is over. Yes, it's cool, but Not Fucking Everything needs to run on blockchain. It's a fucking high-tech ledger.
Switched from Gnome to Xfce on both my home and work computers. I definitely like it better. The things I use are more customizable, and the flashy useless bits are gone.
Mostly, I think it reflects the way I work. I don't need flash, I just need to be able to get to what I need quickly and without any fuss.
I've done KDE before, and I liked it well enough, but it seemed like I was always screwing around with it to get just what I wanted.
I hate arbitrary limits in software.
Today's insanity:
Another team: we're getting poor performance to your systems, how long will the outage will be to cluster X.
Us: We retired that cluster three months ago.
Them: Oh yeah, that's how long this has been going on. Why didn't you warn us?
Us: First, we shut the cluster down three months before actually retiring it, so anyone who had a problem would notice, and could tell us about it. Second, we sent out a company-wide email telling everyone we were doing it.
Gaaaaahhhhh!
Me: "Unit tests are awesome, everybody should write unit tests for their code, here let me give a conference talk about unit testing!"
Also me: *spends an entire afternoon manually making the same four changes to dummy input data*
When I was younger, I would do work software projects into the wee hours, every day.
As I got older, I started having more respect for my own time. And I learned that code done after working long hours was generally of lower quality. (Buggy as hell.) So I mostly work my 8-9 hours, then knock off, unless there's an active prod issue.
But still, now and again, some problem or task will stick in my head, and I have to keep going until I solve it.
