1,317 karma · joined November 3, 2020
As a small business owner in electronics manufacturing, I have decided not to incorporate a GmbH. It’s not worth the hassle. There is bureaucratic rot everywhere and the number of regulations is only increasing. Even trying to export products outside of the EU past 1000 EUR incurs unnecessary processes that have costs and delays. Why?
Then you have this progressive righteousness that has fuelled deindustrialization in Germany which is simply insane, and the fact that political leaders entertain this nonsense is dangerous. Germany missed the mark so heavily and it will cost decades.
I would like more transparency on how long each device gets updates for, similar to how Apple handles their products.
Australians need to care more about improving society - not just the media landscape but in so many facets. Its not going to fail-forwards for much longer, and the cracks are showing
KiCads open format is much better for small business, freelancers and startups and while Altium is industry standard, I can’t imagine it will be for much longer
Thats a massive amount. I had pericarditis, thankfully recovered. I knew a handful of people who also had the same, or myocarditis, none of which died. A friend of mine had to has his heart “drained” of fluid, which was probably the worst case.
Vaccination was sold as being completely safe and was irrefutably coerced in Australia - stripping jobs from unvaccinated people (even if the job was a remote one). Who in the government is going to take responsibility for that? Probably nobody.
And as a result I’ll never trust these institutions again.
As a application developer you have the luxury of relying on the underlying frameworks to do most of the leg-work for you. As long as you follow basic principals within the framework you can have a reasonable degree of confidence that your application will run and the end product will probably be OK. Things like iOS development are so heavily streamlined that sticking to the docs will mean from a technical perspective the app should be fairly solid.
Of course, it does depend on the application because you could be solving complex problems that are outside of the framework, so I'm not dismissing the engineering definition entirely, but generally speaking I think most developers are developers, not engineers. Developers leverage existing systems and build on-top of them.
Juxtaposing the idea of a web or iOS developer with an electronic engineer that is building a physical product with a microcontroller. The application is written in a "bare-metal" embedded environment which generally only relies on a Hardware Abstraction Layer (which basically just maps memory locations and may provide initialization code for various peripherals) and virtually nothing else. The application will likely need to employ interrupt handlers with safety (Mutex/Semapores etc) that must execute within time restrictions or the system will crash, complex DMA buffering techniques and integration with other hardware using physical layer protocols (SPI, I2C, I2S, 802.11 WIFI, USB, etc). The transfer protocol chosen will have its own trade-offs, such as speed vs noise and then noise compensation techniques will need to be used such as increasing the spacing between PCB tracks, using ground planes etc, but these then also have trade-offs because your device may have space restrictions.
The list goes on for a while, and every decision that is made eventually enforces a limitation somewhere else in the system. Engineering (in my mind) is about the balancing of these decisions/limitations to ensure the system runs harmoniously and within the defined constraints.
This is coming from an EE gone web developer who now works as an embedded and hardware engineer. There are trade offs in engineering disciplines that you don’t generally find in highly abstracted web development environments.