The marketing culture for announcing hardware exploits is so strange to me. The norm seems to be getting a custom domain, logos, demos, an FAQ... why do all this instead of just reporting the exploit and releasing a paper?
289 karma · joined July 29, 2020
But I know I, and everyone else posting in this thread, are in the minority. It's clear that most people prefer algorithmic drip in a walled garden. There's a reason everyone flocks to those platforms when RSS superseded them. I don't think I need to re-hash why those platforms are bad for the health of the internet and society as a whole.
So what can be done at a structural level to fight this? What can be done to incentivize people to leave these algorithmic drip feeds to reverse this trend?
There are a non-negligible number of my coworkers who don’t use the licensed LSP implementation and they write all their code in vim – or worse, gvim through a VNC. It’s very easy to tell that their code quality is worse.
My hack was to take a picture on my phone, have Apple's image recognition copy the string to my iCloud clipboard, and I'd paste it on my mac.
It's too easy to defeat the purpose of these things if you're even slightly driven.
But if you replace that term with something like "virtue" or "eudaimonia" and read from that perspective, there can sometimes be some truths to glean from his writing. Nothing really novel, but interesting to read nonetheless.
Alias: artisanspam
Interests: Philosophy pertaining to both political theory and how to live “the good life,” cycling, violin, piano, jazz, PC gaming, design of the built environment (city design, interior design, landscaping) and how it shapes you, meditation, Buddhism (from a secular perspective)
Language(s): English
Link to something you think is cool: Pertaining to built-environment design, I find this YouTube channel interesting: https://youtube.com/@nevertoosmall
Contact info: in bio.
This has been something I wish was available for ARM pseudocode. It’d be ideal to just generate an equivalent Python, SystemVerilog, etc. library from the ARM ARM instead of having to reimplement a subset of it yourself.
However, I do have some problems that you may want to consider pivoting to or adding in the future:
1. A wrapper that works with all of the tools that EDA vendors offer as a back-end. Basically, CMake for SystemVerilog where I can just run `make` and compile, elab, and sim run in order. Every company I've worked for has made their own wrapper program which essentially re-creates this process and I've had to relearn it several times. If you had this wrapper, then you could easily just use other CI/CD pipeline which calls this tool. Bonus points if you can integrate it with VUnit or SVUnit unit testing frameworks.
2. SystemVerilog code generation. Something smarter than just "I wrote a Python script that prints SystemVerilog code to a file based on some config file and then you run your build with the file the Python just printed."
I'm sure there are others that I am not thinking of. But overall, I don't find a lack of CI to be the problem. It's the lack of tools that a CI pipe uses that's the problem.
ETA: Also, was it intentional to launch right on the tail of DVCon? If so, clever planning.
I don't think this'd have the incentive that you're suggesting it would unless something else is done, such as increasing the tax overall.
As other commenters have said, it ends up more like a stream of consciousness and not something well thought out. My word choice isn’t as good. The prose just kind of sucks. I don’t learn much about myself from these sorts of entries.
This is something I’ve simply accepted will happen because I do this on days that I don’t have time to sit in front of a keyboard for 30m. Maybe having more well defined prompts would help improve the quality of these entries. I’m not sure.
I'm only able to function because my partner is taking such great care of me. I would otherwise be toast. I can't drive like this. I can hardly walk due to road rash on my legs.
Take your health seriously. You can only truly realize how lucky you are once it is gone.
Can you elaborate?
But a simple example is `vzeroupper` followed by anything that writes a secret to the same register file entry would be leaked on a subsequent flush.
I don't think the question that ambitious people should be asking themselves is "what is work that I can do that will be great?" but something more akin to "what is work that I will find fulfilling?" Why do you want your work to be great? Do you think that the work being perceived as "great" is fulfilling in and of itself? What are you trying to prove through this work, and whom are you trying to prove it to? These are important questions to ask yourself because, otherwise, you're going to end up getting burnt out and wondering what all of your effort was really for.
A personal anecdote: when I was younger, I wanted to be great at piano. I played it since I was very young and I spent many hours playing it through my teens. I competed against others at music festivals with moderate success, and I wanted to continue doing great work with it. But this environment put me in a terrible headspace. I would frequently have angry outbursts when I made minor mistakes while practicing. If not anger, I'd chastise myself to the point of crying (I firmly believe this is what gave me low self-esteem through my college years). When someone would tell me to take a break given my emotional state, I'd firmly say no and go back to practicing because... why would I stop? The best piano players practice for hours a day non-stop. I'd spent so many hours practicing and I was actually pretty good. I wouldn't be able to do great work if I were to take a break.
It made me a competitive asshole, a sore loser, and a depressed individual.
Ambition is still an admirable trait to have because, among other things, it demonstrates that you have curiosity and a love for life. But point I'm trying to make is that being ambitious for great work simply because you want to do great work is not a healthy way to do your work. You need to have a deeper reason for why you've chosen the work that you do, and you shouldn't fall for the romanticism that these sorts of essays put forth.
The work that you do will be great work if you have a reason for doing it other than "I want to do something great."
Bicycle maintenance can be annoying, but it doesn’t seem nearly as time-intensive as motorcycle maintenance. On the other hand, the process of cycling feels better to me compared to being on a motor bike. It’s quieter, slower, and great exercise. I can talk with others. I feel as though I can get into a state of peace on lower effort rides, as well as a state of flow while racing.
Don’t forget his stint at Intel. I met him there and aside from his brilliance, the other thing that stuck out to me is how short he is.
That's not to say that a financial incentive is a bad idea, though. If you capped the amount that a user made per month to the cost of their subscription - $1, then there's no profit for users to make. They're just saving money on the subscription cost.