164 karma · joined August 25, 2019
But I don't disagree about rootless containers being more secure than rooted ones, just as much as any process not running as root has less privileges then one running as root.
No one should use containers primarily for security ever.
I think if more people would do this exercise they would find that they don't need it, or at least that they might need some form of state reconciliation, but not enough to really warrant all the complexity the tool introduces. Some will find that they don't need it but will still use it for other reasons, like familiarity or because that's what their team uses.
Buying machinery and trying to assemble THD boards at his garage? I know assembling this board would've been expensive, but there is no way that the best decision is to try doing it at home with no skills.
Also, if the sound chip was so available when he first checked, why didn't he just bought it right then? Even one thousand of them would've been cheaper then trying to redesign now. And not only that, he is now thinking of using ANOTHER not currently in production chip BECAUSE HE THINKS IT HAS ENOUGH STOCK! facepalm, just incredible bad decision making.
The only thing this might measure is time you are available to do work, but the same can be done remotely.
A few questions, I saw that the chip itself is surface mount, would I need to make my own PCBs to be able to make more "permanent" projects with it? Also, what kinds of external things I would need to get started, like specific programmer hardware, etc.
With the ESP32 it seems that this is not something reasonable to do, as most things require extensive setup that is implemented in the framework.
So for the simple project I am doing right now I'm using a 8051 microcontroller (AT89S51), mostly because it is super cheap to buy locally but also I am forced to deal more with the details of how embedded applications run. But it does feel like learning 8051 is not too relevant today.
Before this, the devs would make a private channel without product and management people, to discuss technical things openly or just to complain. But product/management was unhappy to be left out of this communication channel.
Eventually we, devs, decided on our own to end the private channel and "banalize" the main team channel, by that I mean that we were going to try to make the main channel less "official" looking and more casual, like sending memes, talking outside of threads and so on. With the intention of making people mor comfortable in using it.
This had mixed to low effectiveness, some people were more comfortable speaking entirely on the main channel, some other people pretty much just started only using private conversations and never used the main channel.
So my solution was to create a temporary project channel, open, but only with devs explicitly invited (but communicated at the main channel that the channel existed). This channel is implied to be a dev channel, but whoever wants to join in can, or they can also just peek in without joining, being a public channel.
So far this has been working well, as long as you are in a reasonably long running project. I have archived more then one of these channels as the projects ended, and I'm thinking of maybe not even achieving the current one and just rename it after the project, let's see.
So, keep of trying to make this fly with your team, it did worked somewhat with mine.
You don't even need to manually switch, you can set a version per folder!
Of course, the thing about bash scripts is that they are super specialized to do one thing, that usually only really works for the creator's workflow.