Perhaps it's my lack of domain knowledge but I am pessimistic about all these magical sounding drugs. There are some horrible diseases out there that are not ageing related that still have no cure and no treatment. I don't know if it's a matter of money, they just sound like really complicated illnesses which humanity has very little understanding of. So things like "reversing ageing" sounds like far fetched when even simpler processes are difficult to understand and control.
I've been reading articles that are telling me how they're prompting from their phone at 2am(and how they know that's not great) and when they're out driving their kids to their activities etc. They say all that as if it's something to be proud of. And what for? Oh they released all these packages that no one is going to use.
Burnout is real and these people have lost track of what's important.
Oh yeah, that sounds wise to me. Some people don't run the agents on a VM on their own machine and opt for a VPS somewhere. And I was wondering if privacy and security had anything to do with their decision.
Is the trust concern for the agent running in any form on your machine? Like in a VM on your machine as well or do you mean on the host itself?
I have read about people giving an agent full access to their main system saying they have nothing of value. To me, that's a strange opinion to have with the distinction between what's private and what's secret.
In my experience, all of this is a reflection of the work or team culture. You can replace the infra cost cutting with bug squashing and write the same article. As in, is the quality of the software something that the business cares about or not? I am not even sure if incentives are necessary if quality is a part of the culture and is the expectation.
In one gig I was on, the culture was all about features, features and more features. The CEO was pushing this culture hard and it showed. You can imagine the kind of product this resulted in. Huge amounts of technical debt, replicated functionality, a high bug count and very high staff turnover. The customers were not happy at all but he just didn't seem to understand or care.
The current price insanity has got me to reconsider upgrading a few systems. It made me think of what I actually need vs what I want, never a good idea for consumerism.
I don't if you know this, but there was a collection for LXD. Last time I checked, it didn't seem very popular so not maintained very well but it did work. Maybe that could be used for inspiration.
I remember Stéphane worked on adding support for incus containers to opentofu which seemed more popular than using ansible to describe the resources.
VM support has been there for quite a while now and works nicely. I think that's what they're referring to. It started out with only system containers and then gained support for VMs and now there's work to support launching OCI images directly.
Can you elaborate on the "software security that US models" seem to have? According to blog posts I read, the code generated had security problems and naive ones at that. Perhaps it got better now or people have learned not to blindly vibe code applications that are to be used publicly but it certainly didn't feel like there were security guardrails.
Extra impressive considering he has a newborn at home.
As an emacs user and fan, I sometimes feel that emacs is pushed into directions it is not meant to handle but the fact that it can be pushed to do so is its power. It's image handling has taught me that, but it also taught me that I prefer to use "the right tool for the job".
This isn't about the first time ever though. I've been hearing the phrase "get rid of your developers" for a long time now. Let's see. SaaS is all you need, boot camp devs, no code, low code and buying-off-the-shelf-components and I'm sure I'm missing a few. This time, the automation is coming to most industries and will be felt across the economy(ies).
I can empathize with the commenter you're replying to. I still read for pleasure and have to read constantly for work of course. On some days, I feel like I can't. It is like exercising the same muscle every day which will lead to injury in a short amount of time. Switching to audiobooks or just taking a break does resolve that.
From what I am seeing around me though, reading for pleasure or even to gain knowledge has decreased a lot. I noticed it in adults first and this is being reflected in their children.
For the unresolved photos issue; I am not an iOS user so not sure if there's any application to help you easily achieve that goal on that platform. But in general, you can encrypt the sensitive files themselves(either files or directory).
You'll lose the ability to easily and quickly look at the photos, as in a single click and you're in, but the process would achieve what you want. To view the photos, you can mount a decrypted version whenever you actually want to look at them and can automate some of this process if it is time consuming or you do it frequently. This is all much easier to do on a computer rather than a mobile a device.
On Linux, there's ecryptfs. There were a few other similar tools in various states of maturity and maintenance when I checked. Perhaps look into something similar for your platform.
Shorter work weeks don't mean less work though. Not from the point of view of management, at least. It just means that 5 days are now compressed to 4, probably making the problem much worse and burn out much more likely.
In my experience, this is what ended up happening.
You mean there's no excuse for cooldowns? Yeah, there is. Security consultants have for years been saying that you need to always keep your dependencies updated. This is often parroted without any context of whether a package needs to be updated or not.
And what's a proper cooldown? 1 day? 3 days? 1 week? 1 month? If you have a vulnerability, now you're exposed during that cooldown period. There's no straight forward or easy answer here.
I am speaking from my own experience here with having to sit in during these discussions where security "advice" is provided to the development team without understanding what it entails or any tradeoffs. I found that keeping things relatively secure is hard work and needs to be a part of culture.
I wonder that too. I've been on the receiving end of "it's 90% done, we just need someone to get it over the line for us" way too many times to know that there's going to be a lot of pain trying to maintain or re-write parts of anything that is vibe-coded.
On the other hand, I notice the AI-fundamentalists(I am not sure how to refer to people within that group) just say that you won't be doing any hand coding anymore and you'd "just" ask something like claude to maintain it or re-write.
I've only seen pip give up twice and both times were due to bugs that were actively being worked on and the project dependencies were quite old. Perhaps that's why I am less impressed. Don't get me wrong, working faster without any downside is great. But I don't change dependencies all that often for it to matter if it does it in 5 seconds or 30.
"holy sacred programmers" and writing "the same functions again and again" are two extremes. There's a point in the middle where you implement the same function twice perhaps and then on the third time feel like such a thing should already be there and so go look or maybe perhaps add some documentation or centralize functionality to a utilities library etc.
I believe the point being discussed is the scale of "badness" that vibe-coding introduces.
Website: http://codedemigod.com Email: [email protected]
Side projects:
- https://moneytracker.codedemigod.com/ - https://aussieshopper.codedemigod.com/