Yeah, a common stupid requirement. Perhaps a selling point for any solution would be to deploy a common serialization/de-serialization package that can be used on both the cloud and end point side.
No, not particularly. What I find amusing about Katsu is it reminds of the 1970s curry in a packet type of meal for example https://nostalgiacentral.com/pop-culture/food-drink/vesta-cu.... Also school dinners where a curry sauce would have a random sultana and a bit of carrot in it. Wonderfully disgusting.
Certainly chicken is increasingly popular, fish and chips is almost a boutique food these days since fish is expensive and also very easy to make badly. Whereas chicken is cheaper and easier https://archive.is/Mu1DL
Wouldn't it be a problem for Nest devices running on Fuchsia OS to get the hardware support they need? Most companies building consumer electronics products rely on hardware vendors to provide working kernels, drivers, etc. Speculatively, if you were able to leverage Android/Linux hardware support without the overhead of the rest of the Android OS, that would free up Nest from having to handle that problem.
If you're new to this area, I would first start by understanding which profiling tools you can use depending on the OS, languages and systems involved.
Even if your system is not C++, I've always enjoyed this talk and the subsequent discussion which tackles some of the problems associated with some programming practices and the impact on performance.
If it helps I think you're right to take this approach.
In my experience defining error as 'handled' or handleable in code can often not be particularly helpful. Are the values from errno(3) always considered as handled?
EINVAL is almost always in "your" terms a fault, ENOSPC or EPIPE likely could only be handled as complete failures.
What I see too often is code which which propagates
The best product manager I worked with was just an exceptionally bright person, they were able to understand complexity of implementation (and even have a reasonable chance of doing it themselves) vs understanding the business need. Just basically a value add to the company without being an engineering manager.
Unfortunately most product managers are just people who sit in the role. They are just gatekeepers who take either credit or blame. They often have little skin in the game.
Overall, if you have a product management organisation, you're doing it wrong.
Since I only use reddit logged in and having the user preference set to the old UI, the most effective way for me to go cold turkey is to logout. Any twitch response to back to reddit presents the newer layout and I'm instantly compelled to close the browser tab again.
In my opinion, it always helps if you get to know the people reviewing your work personally. Sometimes, this happens naturally. You don't have to be buddies; however, if you understand a person's background, biases, and experience, it adds a lot of context to anything they say.
What to Submit
On-Topic: Anything that good hackers would find interesting. That includes more than hacking and startups. If you had to reduce it to a sentence, the answer might be: anything that gratifies one's intellectual curiosity.
Off-Topic: Most stories about politics, or crime, or sports, unless they're evidence of some interesting new phenomenon. Videos of pratfalls or disasters, or cute animal pictures. If they'd cover it on TV news, it's probably off-topic.
Indeed. So imagine doing performance profiling on a 90s UI framework from Psion and then getting feedback from S60 three months later after an integration cycle that you have a core perf or latency problem.
No, the OS was a mess. The UI split was the root of the nightmare.
Nokia were "running" (perhaps should read ruining) Symbian well before they bought it. They were only one of the four or was it five co-owners, but they ran rings around the others when pressuring Symbian leadership. They were the only phone manufacturer with a dedicated product support org, and their pre-prod devices were available in core engineering teams unlike Moto et al. Nokia were the key players to create a Symbian OS core without a coherent UI (Techview lol), no TCP/IP stack, no telephony stack. They helped reduce Symbian OS to swiss cheese because they were so concerned with with recouping their investment from gen 1 SOS products and terrified their competitors at the time got a tiny leg up.
I suspect you're over indexing on what what a person being stalked would do with code. The source code is a tool, and it can become clear to people outside of the corporate interests what the security model or lack thereof is.
I'm curious whether you think there is any benefit for tracking technology to be proprietary.