After trying all the digital options I’m on to a pocket notebook. I carry it instead of a wallet. Great for jotting down that half thought or random todo.
Long running tasks that get rewritten enough times get put in the calendar or a reminder. Anything else that seems important goes in the personal wiki of choice but honestly a lot of the notes are just ephemeral and don’t survive when I switch to a new notebook. And that’s perfectly fine!
Yep and with the CDK it's not only easy to spin up, it's super easy to connect services to it.
I wrote a notifier for when a local business has open appointments. A quick fetch every day and connected it to SNS seamlessly. Now I can easily add family members if they want the notifications and they can easily unsubscribe right from the email. All within the free tier.
I've definitely used the vscode remote ssh functionality before when I've had to use a particular architecture (x86) while I was developing on an M1 mac. In cases like this I already have the dev environment configuration setup for local dev so it's super easy to spin up an EC2 instance and I'm off to the races.
I definitely see the use case, but in saying that I find local development really valuable and default to it when I can. I do however run dev work almost exclusively inside a container so I'm flexible either way. I can see how some might not be.
I feel like option 4 is about the only one with somewhat sane indentation. At least in conveys what level the nesting is on for the root nesting element.
This makes some sense to me. I can see this being a loose part of the CDK since there are quite a few constructs that require local Docker builds before being deployed. That's not just containers either, python lambda code is packages using a Docker container and the result spat out as a zip file for instance.
The last thing I want is to raise the friction for writing down documentation.
It's hard enough to get technical minded people to contribute to a git (or style) based knowledge base.
Pick your poison I guess but I'm quite happy to have testers/BAs/directors/etc able to quickly jot down thoughts roughly than have it disappear into the ether.
AWS has its lightsail range of products which offers exactly this. A much more simplified and opinionated set of products and much fewer knobs to turn.
I pretty much run every project now through a docker compose file and use vscode remote containers with a devcontainer.json file.
This has been immense not only for my own development (nothing on my local machine, everything can be destroyed and rebuilt in a few minutes) but also for onboarding people onto projects. No mucking about with IDE settings, they are free to use whatever of course but having the basics all there makes for a great system all around.
I've been searching for something like this. JSX templates but compiles completely down to static html. Closest I found was `lume` from the deno ecosystem. It's mostly fine but you can be a little hamstrung in what js libraries are compatible.
For me at least the Nix ship has sailed. I'm all in on containers for both prod and local dev environments. Yeah the MacOS performance for volume mounting sucks but we can largely cope.
If the Nix story was more together a few years ago I might have been swayed. Currently though containers is good enough.
Who knows maybe it is worth using Nix when it comes to ARM devices. We'll see I guess.
Long running tasks that get rewritten enough times get put in the calendar or a reminder. Anything else that seems important goes in the personal wiki of choice but honestly a lot of the notes are just ephemeral and don’t survive when I switch to a new notebook. And that’s perfectly fine!