During the attack window, malicious firmware versions were distributed to users who updated their devices. This compromised firmware contained vulnerabilities that allowed unauthorized access to device functions. We have confirmed that approximately 74,00 devices received the affected firmware before our security team isolated the compromised systems.
I get that you want to be "open", but is everyone involved in these transactions ok with them being shared?
Even if they are, this doesn't seem like a good idea security wise. I see partial account numbers and other IDs/numbers that I assume you'd prefer not be public, regardless of how insensitive they may seem now.
EXPENSIFY, INC. VALIDATION XXXXXX5987 THE HACK FOUNDATION
+$0.89
FRONTING $10,000 TO CHRIS WALKER FOR GITHUB GRANTS MADE FROM PERSONAL ACCOUNT
-$10,000.00
This isn't the first time an article is also marketing. Besides, what is wrong with marketing something via a use case article?
This is a fairly tame example of it and I found it an interesting and useful read, knowing full well it was also marketing.
I did a lot of testing with Krea. The results were certainly very different than flux-dev, less "ai-like" in some ways and the details were way better, but very soft and bit washed out and more ai-like in other ways.
I did a 50% mix of flux-dev-krea and flux-dev and it is my new favorite base model.
Anything the requires me to use a different IDE is a non-starter for me.
I can imagine it is a lot easier to develop these things as a custom version of VSCode instead of plugins/extensions for a handful of the popular existing IDEs, but is that really a good long term plan? Is the future going to be littered with a bunch of one-off custom IDEs? Does anyone want that future?
> Hot take: if your job can be partially or wholly eliminated by AI, that’s a GOOD THING. If your job has patterns that predictable or labor that routine, AI automation is a GOOD THING.
The article never says why this is good. It just states it then moves on.
> As a whole, I’m sure it’ll give birth to entirely new systems we haven’t even conceived of yet and, one can hope, free up that time and energy towards more meaningful or creative pursuits.
The people's who job it takes probably don't give af about the patterns of their job, or creative pursuits they can do while unemployed. They are probably just trying to pay their bills and feed their kids.
> one of the worst misconceptions in product design is that a microwave needs to have a button for every thing you could possibly cook
"Worst" is a stretch. Not to mention these often actually do more than just power and time. For example detecting humidity and/or varying power over time.
> You can just have a time (and power) button. People will figure out how to cook stuff.
You could, but people don't always want to figure it out, especially when they are hungry.
This would have been a better article if the takeaway wasn't basically "people are smart, make them learn the underlying structure".
I think good design is recognizing when and how to either expose the structure or paper over it, all while making it pleasant to interact with for all users at either end of the spectrum of willingness to learn it.
For a bike, it pays off to learn. For other things maybe not so much. Combining these two very different cases and then making a blanket statement that "Good designs expose systematic structure" doesn't land well.
I think the microwave ones are useful even if they are just presets for time and power.
With a new bike, you can get a feel very quickly for what "5th gear" works well for and experiment with it and get immediate feedback and try other options pretty much no downside.
With a microwave, I don't necessarily want that level fine grain control. I probably just want to eat and not ruin my food and I certainly don't want to spend time running experiments. Having a preset at least gets you in the ballpark.
I've tried to watch Louis many times.. can't do it. He is just so whiny and annoying, it is really off putting to what might be otherwise interesting topics.
200k/yr revenue?
Like others have said - basically they can't afford to do the things you want to do. All the things you want to do take time to make run smoothly and divert dev attention for a while, and it seems there is no time for that. It all may help in the long-run and actually help generate more revenue, but that won't matter if they go under in the meantime.
If you don't like that yolo culture, move on... you are not likely to change it.
^ this. If a junior dev is legitimately interested in software development and how things work, they will use these tools for more than just completing their tasks and a paycheck and will eventually stand out above their peers who don't.
If the author is suggesting that more junior devs today than in the past are only interested getting tasks done and the paycheck, then this really has nothing to do with AI.
I can't really speak to the impact on junior devs since I haven't worked with any since the start of AI dev tools so this comment is kind of off topic.
Totally agree that should be treated as learning tool just as much "give me something that works" tool. If Junior devs are not taking advantage of that side of it instinctively out of their own curiosity and interest, well, maybe they were never going to be good developers in the first place even without AI.
What I can say is that for me as a as senior dev with 22 years experience who has been using using these tools daily for about a year now, it has been a huge win with no downsides.
I am so much more efficient at unblocking myself and others with all the minor "how do I do X in Y" and "what is causing this error" type questions. I know exactly what I want to do, how to ask it, but only partially what the answer should be... and AI takes away the tedious part of bridging that knowledge gap for me.
Maybe even more significantly, I have learned new things at a much faster rate. When AI suggests solutions I am often exposed to different ways to do things I already knew, features I didn't know existed, etc. I feel good that I found a solution to my problem, but often I feel even better having learned something along the way that wasn't even the original goal and it didn't really take any extra dedicated effort.
The best part is that is has made side projects a lot more fun and I stick with them a lot longer because I get something working sooner and spend less time fighting problems. I also find myself taking on new types of projects that are outside my comfort and experience zone.
The technical reason was “for loss of trust and confidence in his ability to execute the responsibilities of his command” which is not related to him following the book or if the book is right or wrong.
Which makes sense. It was subjective and that is ok.
“As a commander you serve at the pleasure of the commandant,” Del Pizzo said. “It was an absolute privilege to have the opportunity to lead the Marines, sailors and civilians of VMX-1.”
also
“he made the decision to relieve the commanding officer of [VMX-1], due to the unique mission of VMX-1.”