No, it's day trading and picking stocks which is betting against wall street firms, obviously that's not the way to go. But that's not all of investing. If you are diversified and tune a portfolio for risk, it's more like a bet that the long term trend will be for the global economy to become more productive as time goes on. And this is usually true, besides the transitory periods of recession.
I've played a bit with weggli, it's pretty useful for "grepping" an entire codebase for patterns (for example, to search for antipatterns in a codebase)
Perhaps more capable but also more complex is clang-query:
I would think if you depend on data stored in a container being persistent, it's an indication you really should be mounting a volume to the container and persisting the data there. Then container restarts won't matter. Best practices are generally for containers to be "cattle" instead of "pets", and data persistence usually has a different solution.
Regarding using a container for distributing static site generators, does anyone really do that? I think you may be building up a straw man here, I haven't seen anyone recommend this workflow. Could you elaborate on how this relates to the parent comment's mention of using less space when running many containers? What the parent comment mentions is, in fact, highly relevant to some of the main use-cases of containers, which is running many containers of the same service on one or many hosts. Space can be saved there with layer caching.
> Could you elaborate on how this relates to the parent comment's mention of using less space when running many containers?
Could you elaborate on how does "running many containers" relates to the topic of distributing and running *a single tool* (that was the context of the article)?
> Could you elaborate on how does "running many containers" relates to the topic of distributing and running a single tool (that was the context of the article)?
YOU may be distributing just a single tool but your users most likely use the computer for more than one tool. If they use many tools under docker, it is likely that many of those tools share the same underlying layers.
I completely agree--in my day-to-day, I'm very much in my head about the problem at hand. I respect folks who can keep the long-term vision in their sights while applying that to short-term decisions which will help in the future. Some of the more valuable things I could learn from the higher-ups at my work, I feel, are related to big goals, changing landscape, rising opportunities and problems in the industry.
I think that is natural to be in your head about the problem at hand, especially if you are busy at work it is hard to think about the bigger picture!
Curious, do you have any thoughts what senior leadership can do better to ensure we have that outlook? The only thing I have ever seen at previous companies was quarterly Town Halls where we discuss the company outlook but I never feel that is enough!
Yeah it's definitely a balance--the big company-wide meetings can be good for context but could also be too broad in scope. On a couple occasions I've enjoyed medium-sized informal get-togethers with my team, and I can sort of pick people's brains. Just having that social environment means I can sometimes talk one-on-one with folks I would rarely interact directly with otherwise.
Pretty sure they meant Guix the OS not the package manager. The OS uses GNU Shepherd. Of course if you install the package manager on another OS, you get whatever that OS chose for an init system.
It's possible this is including many misclassified listings (e.g. hourly paid internships). Additionally, I've seen some listings for higher level jobs for absurdly low salaries ($19,000) which I can only imagine are typos. I wonder if the average somehow includes other regions too with very different cost of living. I wouldn't put too much stock in those average numbers. If you are looking to get an idea for the market for entry level SWE positions, it might make sense to narrow the search to known companies in your region.
For what it's worth, with many Hugo themes, it is possible to add a "Disqus" (or other provider) comment section to posts by simply adding a token to the static site's config file. See: https://gohugo.io/content-management/comments/
This is also possible with other static site generators like Hexo and Jekyll.
I didn't even know what "immobilizer" meant in this context before hearing about the issue with Kia and Hyundai a while ago.