I don’t get all wrapped up in imagining sharing the experience or anything like that, but it’s always nice to get a factual update about the other person. And if they have something interesting to say about whatever it is, that’s good too.
I don’t get all wrapped up in imagining sharing the experience or anything like that, but it’s always nice to get a factual update about the other person. And if they have something interesting to say about whatever it is, that’s good too.
Someone whose interests align with yours and who is more active in the organization so they follow the issues more. E.g. a board member or staff member, etc. It depends on the org too, of course.
Usually you just appoint a proxy to represent your interests in a given organization, I thought.
Fair enough. If your product isn’t safety or security critical then it’s mostly a matter of getting it working and passing reasonable testing. If it’s critical you might look for outside help or review, and maybe revisit the decision to use C.
The book “Analysable Real-Time Systems: Programmed in Ada” was recommended to me and looks good. I have a copy that has been on my reading pile for ages. I was just thinking about it recently. It could be a source of wisdom about embedded dev in general, plus Ada generally fosters a more serious approach than C does, so it could be worth a look. I also plan to get Koopman’s book that I mentioned earlier.
Jeez. Maybe cool it for a while.
Why another reddit competitor? There is already Lemmy.
Unihertz Tank 2? I sort of want one of those. The Doogee’s battery isn’t especially above average these days. The Motorola budget phone I use now has 5000 mah.
I’ve thought of configuring an Anduril light for just on/off. It is somewhat doable without reflashing.
Hard to see why to get this over a more mainstream phone where you can at least hope the software is not too flaky. Unihertz has some phones with special hardware features like tiny size or huge batteries. Doogee has had some of those phones but this one is just normal, 5100mah presumably non removable battery. Ok 20gb ram, but who cares? No price mentioned.
Doogee, make a phone with removable 18650s and I’ll pay attention. Or a phone that runs GrapheneOS out of the box, or anything interesting like that. This isn’t it.
Here’s a more informative article with a link to the paper, which is in a Chinese journal. The link doesn’t open for me rn but it’s a start.
I spent a few minutes looking for the research paper, no luck. But it doesn’t sound like something to worry about for now. D-wave isn’t a general purpose quantum computer anyway. You can’t run anything like Grover search on it.
What are you working on and what kind of organization? Are you working with someone more senior? You could ask him or her for an assessment of where you should work on strengthening up.
You are in the right mindset if you are worried. Many C programmers greatly overestimate their ability to write bug-free or even valid (UB-free) code.
The AVR MCUs are pretty simple compared with 32 bit MCUs, so are good for asm coding.
Otherwise it’s a matter of coding til it’s reflexive.
Philip Koopman has written a book on MCU programming that sounds good. I haven’t seen it yet but someday. You might look for it: https://betterembsw.blogspot.com/2021/02/better-embedded-system-software-e-book.html?m=1
John Regehr’s blog is also good.
In C in particular, you have to be very cognizant of the tricky ways the language can screw you with UB. You might want to try some verification tools like Frama-C, use UB sanitizers, enable all the compiler warnings and traps that you can, etc. Other than that, I think using too many obscure features of a language is an antipattern. Just stick with the idioms that you see in other code. Take reviewer comments on board, and write lots of code so you come to feel fluent.
Added: the MISRA C guidelines for embedded C tell you to stay with a relatively safe subset of the language. They are mostly wise, so you might want to use them.
Added: is your issue with C or with machine code? If you’re programming small MCUs, then yes, you should develop some familiarity with machine code and hardware level programming. That may also help you get more comfortable with C.
Thanks yes I might look at the paper. Having a mixture of stable and chaotic regions is a well known phenomenon though. See for example Wada basins.
I thought this type of thing was well known in chaotic dynamics. There must be a new discovery here, but the phys.org article is not much help in explaining what it is.
Federation protocol is pretty simple and coding it could be a fun project for someone. Do you have software that you’d like to use? It seems like a good companion to a static site generator.
I wouldn’t say she’s bad or non-credible. Her viewpoint is in a minority but is legit. I just guessed it was her because she keeps harping on the same points and I’m like, ok, we get it. She wrote a book saying the same thing too. Maybe it’s worth reading, idk Some perfectly good physics is inherently not falsifiable though, like general relativity’s predictions about black hole interiors. So she is a bit too hung up on that issue.
Without clicking I immediately guessed this was Sabine Hossenfelder.
Well I mostly meant the characters themselves are male projections as a result. So they are effectively dudes with curves a lot of the time. I’m having trouble thinking of exceptions who aren’t caretaker types like Deanna Troi. I probably don’t read enough contemporary fiction.
Lame. 45 days? 10 days for DCV? How common are exploits involving old certificates anyway? And automated cert management is just another exploit target. Do they seriously think an attacker who pwns a server can’t keep the automatic renewals running?