As far as I'm aware, he went by he/him/they/them and accepted all of them.
406 karma · joined February 23, 2024
The Depression post was one that resonated with me and kept me thinking of the quote from True Detective, "Life's barely long enough to get good at one thing. So be careful what you get good at."
Zsh is cool to look at and has a couple useful plugins, but the whole thing slows down your shell start up and adds a slew of dependencies that may go on life support, or under control of a foreign government.
I'll just stick with bash. It's ugly. It doesn't have pretty auto suggestions but at least it works and it will be there forever.
The correct name would be "useragent".
Make a cronjob monitoring service. Make a "privacy focused analytics" platform. Make a session replay service. Make a "javascript error collection" service. Make a user feedback widget as a service.
It doesn't matter what you make. Pick something that has been done before and do it on your own.
If you are hell bent on live streaming-- live streaming that would be far more interesting than watching someone rebuild react.
People have incredibly short attention spans these days. If your video isn't 20 second shorts with large text and jump cuts you will lose the viewer.
Video is a terrible medium in general.
You're not Tsoding/T3/Primeagen and you're better off spending your time elsewhere. Note-- their audiences are primarily young junior developers or developers to be.
For reference, my Github is set to private and has a single repository pointing people to my personal site. My personal site has 8 sentences on it. It says who I am and what I've built (software products). I don't blog. I don't share code.
What you need is to be able to demonstrate what you are capable of. If you have it in you, it's even better to demonstrate you are not another code monkey that is more interested in 1s and 0s than humans.
My suggestion (biased, from what I've done) is to build one or more products (ex: a SaaS product, etc).
In the best case your product brings in enough money you never need to work for someone else. In the worst case you demonstrate the ability to build a product geared towards regular human beings.
I'll take that as a compliment.. as someone that took nights to build a SaaS product solo into a multi-million dollar business (and still do it solo).
I never really put it in words before, but I pick up a lot of these signs. From the way someone writes, to the way they text message, to the content they consume, to how they handle social dynamics like grabbing coffee together or a lunch. It all paints a picture of a person and/or team. These things matter.
If they can't take their time to update the deck, they probably skimp out elsewhere.
I stick to buildless libraries and frameworks. You can even build an SPA without one (mithriljs[1], as I used in a browser extension).
If I did, I'd keep it simple. I use Nginx in front of the Go server. I'd likely use the Nginx server as a load balancer and replace each Go service one at a time to have no downtime. It doesn't matter how many ports you use as long as Nginx knows the port range. It will distribute the incoming requests to the Go processes.
edit:
For those wondering why I use Nginx. It's where I terminate SSL and I also use it for simple gzip/compression/caching for outgoing resources.
I don't use Caddy or anything else. I've used Nginx for many years and it just... works.
I'm no Google, but it has been holding up very well (I've never had any issue with CPU, memory or anything). My simple release strategy does come with potential downtime, but the shutdown and start up are so fast it's very minimal.
I have certainly become more of a recluse on the internet. I'm still figuring things out... at this time I think I'll pull more inwards. Do my own thing. Create my own art. Maybe I'll see you on the flip side? Maybe not.
It's incredibly simple and old school. No kubernetes, docker, cdns, etc.
Write code, build binary, ship binary.
Apple is running a HaaS (Hardware as-a Service) and your subscription is somewhere between two to three years.
Also, the Native American LARPing line was pretty dope.
For the uninitiated, the more fucks, the more productivity.. ie, they are looking at the code and trying to do something.
True story-- at my first job the fucks were so bad they moved some of us into our own offices.
HTMX really shines in a few areas for me.
1. Async loading of things (ex: render a dashboard and THEN load the chart data) to prevent blocking page loads.
2. Lazy loading of things (ex: Instead of rendering a modal for every row in a table, fetch and display the modal when the row edit button is clicked).
3. HX-Boost is nice. I have always been a fan of Turbolinks (classic) and preventing full page loads and allow permanent page elements. Boost makes it possible out of the box.
4. It leaves wiggle room for progressive enhancement. For example, if you are lazily loading a modal but JS is disabled, you could open a separate page for the modal/form instead of lazily fetching and displaying in-page. It's more work, but at least it's _possible_.
Alpine on the other hand is nice for different things. I mainly use Alpine for things like handling a dropdown, slideout, animating things, etc.
All of this is done without writing any JavaScript. I am able to stay in my HTML templates or backend (in Golang) without ever touching JavaScript. I also adopted Tailwind for the same reason. I essentially write the CSS in the HTML (with classes) and let tailwind compile and generate the CSS for me... no more unused CSS. No more CSS clashes, naming conventions, etc.
It's a great workflow.
edit:
I just wanted to say I use HTMX with the head-support plugin bundled together. @recursivedoubts, hoping for 2.0 soon to come with support built in :)