I work on a similar product, and honestly the AI parts dont really matter wrt privacy. Its uninteresting. The EXIF information is way more private and useful, but exif data is also what makes the product usable. If you strip exif, you might as well chuck all your photos in a single folder and call it a day. We also dont sell your data to anyone and we dont run analysis on your data
I concur, the slow drip feeding is adequately explained by coming from a place of war ineptitude and domestic priorities rather than a conscious strategy.
Its also a difficult problem. They need the right digger and the right crew at the right time and possibly the right weather to get the job done. Many times there will be weeks of juggling around schedules and suddenly the digging started three weeks after the road was finished
Yeah, its not much I agree. But it is an agreement the company can wave that they at least have future buyers for their non-existing power generators if they were to build them!
A good PM will understand that to get to C, we need to build and support A + B before we can build C, and plan for this. Like, if we built B to be a terrible barely working mess, they understand that this will make C basically worthless. But in my experience, this ability is surprisingly rare.
I have worked in 3 "startups" now, only coming in after they have started making enough revenue to pay normal ish salaries. The thing I have seen the most, is several of the founders have a blurry concept of what were ideas they had, what was actually built, and what of parts of what was implemented actually works.
Yeah, I have been saying this for years now. Debian and Ubuntu type distros starts doing custom patches and cherry picks changes into 3 year old software, just to keep it chugging along. Sounds like insanity to me. Just upgrade so you are not 3-4 years behind, and by keeping the number of custom patching lower, have a simpler time fixing bugs.
Its not awful, but its not good either. Pi4 has been a looooong slog, but they also use components that cant be released under GPL license, so there is not much they could upstream for those components
Hopefully your domain is sane enough that you can read nearly all the data you are going to use up front, then pass it on to your pure functions. Speaking from a Java perspective.
Most are not affected by db migrations in the sense that migrations are run before the service starts the web server during boot. the database might block traffic for other already running connections though,in which case you have a problem with your database design.
Realistically, my advice is. Document as little as possible. Build processes into your tools so it can be tested and repeated. Documentation that can get outdated, will be outdated and even worse be wrong. And, for example APIs can be organized in a way that documentation can be automated, so its never wrong or outdated, by choosing to use API contract first, like Protobuf or implementing via OpenAPI specifications. If you are implementing a specification of some kind, keep a copy of the specification version you have implemented checked in with the code.
Other things I have seen is f.ex. code that implements a business process, also can output itself as a Graphviz drawing, describing the parts of its own structure.
I think it has many good parts. There are waaaaay worse formats I have worked with over the years. Like COM, java RMI, many variants of SOAP, handcrafted json in countless variants…
Failure to consider holistic societal gains is not something new for Americans at least. Both for tax payers and corporations, making any inmate a productive tax payer would be better for society and for shareholder value.
If you have shipped some task to a channel, or is waiting for some work to complete on a channel, there is no native way to propagate the error that your task may have failed. Also if a error did happen during processing the task you put on the channel, the stacktrace suddenly is not the whole story anymore. Channels also has no way to make sure the context.Context is reasonably propagated