Live data from Hacker News

Protect your shed

dylanbutler.dev

41–50 of 89 posts

Re: Protect your shed

#41
post #37

> The shed is where you take the blueprints you learned on the job and actually get to play with them. > You try something in the shed on a weekend because you’re curious. You learn the tradeoffs, the rough edges, the things the documentation doesn’t tell you. Then months later, when the team at work is evaluating that same tool or approach, you’re not starting from zero. These are two opposing concepts, but both Tru…

Can we have a call about your dream? I am in a similar boat. My email is in my profile, and my comment history exists.

No worries if this is a bit too forward. It just seems fun to brainstorm about a dream like this and we may have some complementary experiences.

Re: Protect your shed

#42
post #37

> The shed is where you take the blueprints you learned on the job and actually get to play with them. > You try something in the shed on a weekend because you’re curious. You learn the tradeoffs, the rough edges, the things the documentation doesn’t tell you. Then months later, when the team at work is evaluating that same tool or approach, you’re not starting from zero. These are two opposing concepts, but both Tru…

Can we have a call about your dream? I am in a similar boat. My email is in my profile, and my comment history exists. No worries if this is a bit too forward. It just seems fun to brainstorm about a dream like this and we may have some complementary experiences.

Can I get on this action too? This sounds like a good idea.

Re: Protect your shed

#43
post #29
post #7

Personally, I am over side projects. Did them, the games, the websites, the failed startup thing. I just do other things now. Building finance stuff during the day, doing little computer outside work (a bit of 3D printing here and there). It’s fine. My career’s fine. The work doesn’t suffer from it. Do I have the spark? Idk, I feel I am too old for that spark shit. There is work to do, I do it. If it’s tedious, I’ll…

I think both viewpoints are valid. It's perfectly fine to see your work as a craft which you hone in your personal time, and also see it as a means to an end where you clock in, get the job done, and clock out. It's also understandable that the amount of personal time we have to dedicate to it, and even interest, can vary over time. That said, I think your day job is more enjoyable when you see your work as a craft.…

About the work being more enjoyable when seeing it as a craft: I think it only is more enjoyable, if you can somehow bring part of your craftsmanship into it, and are not overly limited by other people or the sprint or management or any of the other many factors that ruin the fun, like time available, terrible inherited codebase that would take weeks or months to fix, and so on.

Re: Protect your shed

#44

> That’s taking the structural discipline from the skyscraper and applying it to a space where I had total freedom. Yeah, nah. When I take my learnings home with me, it fails every time. Usually, the scale of work necessary to maintain an enterprise-grade system rapidly outgrows the time I can reasonably allocate to it. In other cases, I lose interest because it's boring corporate crap. I don't known how all of you "…

I have a professional 'homelab' and a personal 'homelab'. You're 100% right, they can be a time sink. The important bit is to make sure the time is setup not 'maintenance' time.

The trick is twofold: if it isn't 'declare and deploy' don't run it. If it isn't in your backup/restore pipeline don't run it.

Pfsense and Home assistant are huge pains in the ass. Everything else is easy breezy.

Proxmox/pbs/truenas/talos/linstor/DRBD are all amazing.

I'm thinking about ditching pfsense for tailscale/cloudflare tunnels, but it's not worth the time atm. I don't have a viable alternative for HA.

Re: Protect your shed

#45

> That’s taking the structural discipline from the skyscraper and applying it to a space where I had total freedom. Yeah, nah. When I take my learnings home with me, it fails every time. Usually, the scale of work necessary to maintain an enterprise-grade system rapidly outgrows the time I can reasonably allocate to it. In other cases, I lose interest because it's boring corporate crap. I don't known how all of you "…

The trick is to not overengineer your hobby if you're only doing it to prove a point.

ie. Yes, you could run a full on corporate CA, issue SSL certificates for your domains, manually rig up wireguard and run your own internal corporate VPN... or you just accept that your grand total of 1 concurrent user on an intranet is probably just better served by setting up Tailscale and a wildcard LE certificate so that the browser shuts up. (Which is still not great, but the argument over HTTPS and intranets is not for right now.)

Same with other deployment tools like Docker - yes, there's a ton of fancy ways to do persistent storage for serverless setups but get real: you're throwing the source folder in /opt/ and you have exactly one drive on that server. Save yourself the pain and just bind mount it to somewhere on your filesystem. Being able to back the folder up just with cp/rsync/rclone/scp is a lot easier than fiddling with docker's ambiguous mess of overlay2 subfolders.

Every overengineered decision of today is tomorrow's "goddammit I need to ssh into the server again for an unexpected edgecase".

Re: Protect your shed

#46

> That’s taking the structural discipline from the skyscraper and applying it to a space where I had total freedom. Yeah, nah. When I take my learnings home with me, it fails every time. Usually, the scale of work necessary to maintain an enterprise-grade system rapidly outgrows the time I can reasonably allocate to it. In other cases, I lose interest because it's boring corporate crap. I don't known how all of you "…

I'm actually grateful (today) for the lightning strike that nuked my old pile of servers at home. It freed me from the whole thing in one step. I was completely disabused of any notion that I had control over anything at that point.

You might think you are protected with UPSes and what not, but nothing will stop the electromagnetic effects if it hits within a few feet. Every piece of copper is going to get lit up. No solution is 100% guaranteed here, but EC2 and snapshots is a hell of a lot more likely to survive a single event like that.

Re: Protect your shed

#48

Earlier quoted context omitted.

Hackaday.com comes to mind. That's a blog with those tinkering things. Hackaday.io is a big base where people store their schematics and worklog, present their inventions and tinkering as they happen.

Hackaday is amazing - so many cool, inspiring ideas. It’s been around a very long time too.

It's also owned by Siemens via Supplyframe. That means its content is controlled to a certain degree. Sort of like the way Vice is controlled by its owners. In that way it could function as controlled opposition. Be careful what you submit too.

I wonder if it'd be possible to create a Hackaday-type site with HN content. hackernewsbooks.com >> hackernewshacks.com

Re: Protect your shed

#49
post #14
post #10

The second half of this article is detected as AI by pangram: https://www.pangram.com/history/63fdecd4-f932-4fad-af60-da99...

Ai detectors are bullshit. That said, the second paragraph has the distinctive stocatto tone of AI But AI is shaping how we write, so this could well all be hand written just by someone who spends time with AI output.

> stocatto

Staccato, which is Italian for "detached, separated".

When I see simple Italian words used as technical terms in music or art, I think "oh, this must be what English speakers feel when they work in tech - a lot of common words becoming specific concepts in that particular field".

Post reply on HN