One of the prime rules of storytelling is that the hero has to have a flaw.
Superman is super. He can’t lose. That’s why the writers introduced Kryptonite. Captain America is a super-soldier, but is still mortal. Thor is a god, but can lose his hammer and his powers.
The problem with Superhero movies is that they all got so much power they became invincible, and boring.
Good, classic storytelling beats VFX 10/10.
There should be a Shakespeare play with that plot.
deleted by creator
Pretty cool that he reverse-engineered it and 3D printed the fixtures. Wonder if Adam Savage has any original SFX rigs.
RPN: OR Trick Treat
Async multithreading: Treat Trick (loop closed) OR (stack trace)
That looks awesome!
A few tips, based on what has worked in our local libraries:
A story-reading space where parents or caregivers can bring infants and toddlers to listen to books being read outloud. Librarians, parents, and volunteers take turns as book readers. Hugely popular. Absolutely packed them in. One branch even built a hand-painted replica of the “Goodnight Moon” set.
A separate, private space for nursing mothers.
If the budget allows it, a phone charging station.
Space for common government forms. Applications for welfare, disability, voter, and tax forms. If you can get volunteers to help, even better.
Was going to mention tools, but see you already have it. In ours, you can check out shovels, saws, wrench sets, gardening tools, etc, to take home for a few days. It got so popular they had to move into their own space.
We love our local libraries.
And the one time the rocket goes kablooey on its way up, everyone down the flight path will get a shower of used hypodermic needles, disposable vapes, and old appliances.
I’m feeling attacked.
Plastic, nitrogen (or some inert gas, if packaged), and formaldehyde.
Yum!
http://www.diningdish.net/2016/07/the-biggest-best-bloody-mary-east-of.html
Phillips Seafood, Baltimore Crab Deck.
Don’t bring a knife to a gunfight.
Guarantee someone’s going to generate a bubbly podcast of Mein Kampf or Project 2025.
Now only have to wait for:
to catch up…
There was an appliance where the wifi chip was at the end of the power cable, embedded inside the plug. From the outside, you couldn’t really tell. It was there so radiation inside the box couldn’t affect the wireless signal as much.
I can imagine some genius thinking it’s a good idea to run a server from inside a cable or a connected home appliance.
Ed is getting good at lobbing these darts at hype bubbles.
The thing that this writeup ignores is that the object isn’t to show short-term revenue, but to put all competitors out of business, be the last one standing, and create a monopoly. Either that or get bought out so the investors can move on to the next thing. But at $150B valuation, only MSFT or Nvidia can afford to buy them outright.
Google, Meta, and Amazon burned through cash for years, but they eventually outran all competition and then monetized the users who had nowhere else to go.
If you use github pages, you can create, deploy, and host static websites for free. Only cost, if you want your own URL, is for a custom DNS name.
You can use their default Jekyll static rendering engine, and create the content using Markdown. And with github actions, all you need to update the content is create markdown, then push the change to the same repo. After a few minutes, the new content shows up.
Hugo can also be used, but it takes a few extra steps: https://gohugo.io/hosting-and-deployment/hosting-on-github/
You can also find ‘themes’ to customize the look and feel of the site, specific to the site generation tool.
If you want a lot of extra features, Docusaurus is pretty much as good as it gets, and you can set it up to push out to GH pages: https://docusaurus.io/docs/deployment
OK, you wanted a conversation… :-)
I did read the post, but I assumed it was the starting point of a system or mechanism, not the end-point. Wanting to just run “docker compose up” is fine, but there is more to developing and deploying to production (and continuing post-launch).
That’s why I mentioned the CLI. It lets you go from a simple local app (Django on sqlite) to a Docker one (postgres, celery, redis, etc.), to all the way out to the cloud (ECS/EKS/serverless lambda/RDS), without having to remember what commands do what or managing lots of separate docker-compose files.
I can see we are VERY far apart on how docker should be used in moving toward a production-ready system.
For one thing, recommending putting secrets inside docker-compose is an instantly disqualifying piece of advice. There’s a whole ‘secrets’ section of docker compose that is there to prevent people from inadvertently including those in cleartext and baking them into images: https://docs.docker.com/compose/how-tos/use-secrets/.
Github itself has a secret scanning mechanism to prevent leakage: https://docs.github.com/en/code-security/secret-scanning/introduction/about-secret-scanning. For gitlab, there’s also Blackbox or HashiCorp vault. Putting AWS key/secret inside a repo can be VERY expensive and open one to legal liability if the account is misused. Repeated infractions could lead to AWS banning one’s account.
I really recommend you take down that part of your post, instead of proliferating bad practices.
As for the rest, to each their own.
There’s no real value to any of it.
Attach free beer to point levels and watch this thing explode.