HN user

burstmode

86 karma
Posts1
Comments51
View on HN

If your product has a software-related failure, customers won't care about all of your certifications. Only the end product.

If you're in a market where a ASIL certification is needed, the customers ONLY care about this certifications. I keeps them out of jail.

No, the exact reverse: Hide away the brain-damaging GIT database system behind a proxy, so that I can (again!) concentrate on my job as developer. Instead I have to spend at least one day every week as "version managment administrator" just to keep GIT from falling apart because of weird internal errors. I will never understand why a plain user must deal with internal data structures (like db-indieces) of some tool on a day to day basis.

Many people, Especially sice C++ has become a playfield for CS language theorists, who invent more and more overcomplicated language "features" with little to no practical use.

Every few sentences there there is a remark like "This circuit might have edge cases,... "...perfect for the majority of use cases,..". In other words: It will, at best, work on the developers table, but nowhere else. Why is somebody publishing examples that won't work in the real world ?

Ohh man. The usual crap: Desingers adding unneeded whitepace to show of their super skillz. These GUI designer bros should really limit their work to their own tools and leave the productive part of the world alone.

RT_PREEMT has nothing to do with "real" realtime. You never know WHEN the preemtion is gonna happen. Might be in 20ms, might be in 200.

If somebody lost a commit after a rebase, and nobody nearby could help them recover it, they should consider spending a few hours learning about git.

GIT is the only source control system where you can completly loose commited data by actions (or commands) available the non-admin user. It's funny to see that this is considered a "feature" and not a design failure.

Results of code review of false.c:

* Use of undocumented magic numbers (1)

* No use of getter/setter pattern

* Inflexible design (datatype of result is fixed, no template pattern implemented)

* Manual memory management (no garbage collection used)

* No infrastructure for automated testing included

* No unit tests available

* Code has not changed for Years (code smell!); Probable stale code, to be removed in next release.