I think it's important to share the difficult / hard experiences of having kids as much as the good ones. I've noticed that there is a huge bias towards only sharing the good moments and white-washing all of the bad as something you can "laugh about later." To be frank, not enough people were honest with me about what it would be like having kids before I had them - and I was incredibly upset when I realized that (several years into being a parent).
I now make it a point to be honest with people when they ask "Should we have kids?" and tell them about how hard it can be, etc. Most importantly, I tell people that they shouldn't have kids unless they would still want to do it if their experience doesn't land in the middle of the bell curve. We tend to romanticize the decision, and expect that everything "just gets even better" with kids. There are all sorts of ways your experience can be less than ideal. Unless you're evaluating your decision with those potential outcomes in mind, you're doing yourself, your partner, and even your future children a disservice.
Anyone else surprised that the download links are plain HTTP without SSL? I know it's a page that in the past I would have typically not worried about securing - but nowadays it's SSL everything or else your browser yells at you.
Our company pays for Docker Desktop licenses, but we've made every other effort to not rely on Docker directly (e.g. DockerHub) to avoid the SPF. Pull-through caches with ECR were a quick way to drastically reduce reliance further.
Given the state of our internal tooling, we can conceivably move to podman or similar within the next year if the license fees become onerous, but, given the size of our org, we likely will just keep forking over license fees as it's cheaper than the salary to remove the dependency.
This seems to work really well in cases where you're just laying down boilerplate. A few cherry-picked comments seem to suggest that React components are an ideal use case - which makes sense, that's a lot of munging and syntax to just render some strings.
However, I find the process of writing these sorts of functions cathartic and part of the process to get into zen-mode for coding. I think I'd feel less joy in programming if all of this was just done by glorified commenting and then code-review of the robot.
I like to think of coding in terms of athletic training, which usually is comprised of difficult tasks that are interspersed with lighter ones that keep you moving (but are giving you a bit of a break). Training for soccer teams often involved lots of sprinting and aerobic exercise - and in between those activities we would do some stretching or jogging to keep our body moving. These sorts of small functions (write a function to fetch a resource, parse an input payload, etc.) are when my brain is still moving but getting ready for the next difficult task.
https://aws.amazon.com/blogs/database/reduce-your-amazon-ela...