hkwerf
Location: Munich/Rosenheim/Bruckmühl, Germany (GMT+1)
Remote: both remote and on-site possible; anything more than 50 km from Munich should be at least 80% remote due to family; separate and lockable ESD-safe lab space with measurement instruments is available
Willing to relocate: Unlikely
Technologies: C, C++, Rust, Python, TypeScript/JavaScript + many more languages; {software, electronics, FPGA} × {architecture, design, simulation, implementation, integration, testing}; continuous integration (Gitlab CI); Linux (Buildroot, Yocto, containers, kernel, boot and board setup, parallel and real time operation), Bootloaders (U-Boot, Barebox, etc.), bare metal + several RTOS; networks (everything from obscure Ethernet variants over IP networking to REST APIs), fieldbuses, and internal buses (PCIe, SPI, I2C, UART, etc.); relational databases (SQLite, MySQL, PostgreSQL); engineering and project management according to medical device standards (FDA and ISO/IEC);
Résumé/CV: Full résumé available upon request
Email: [email protected]
Hello, I am Johannes Agricola, a software engineering consultant based in Germany (GMT + 1), but available worldwide.The previous decade of my career was mostly focused on embedded software and digital electrical design. I have had particular success implementing medical device electronics and software. I have guided this development through the hoops set by FDA and international medical device standards both as an engineer and a team lead.
I am:
- currently looking for freelance contracts,
- quickly picking up on new contexts and generally able to productively contribute to most projects on day one,
- open to both short and long term involvements.
I am in particular also available for short-term support for teams needing to meet tight deadlines.
Remote: both remote and on-site possible; anything more than 50 km from Munich should be at least 80% remote due to family; separate and lockable ESD-safe lab space with measurement instruments is available
Willing to relocate: Unlikely
Technologies: C, C++, Rust, Python, TypeScript/JavaScript + many more languages; {software, electronics, FPGA} × {architecture, design, simulation, implementation, integration, testing}; continuous integration (Gitlab CI); Linux (Buildroot, Yocto, containers, kernel, boot and board setup, parallel and real time operation), Bootloaders (U-Boot, Barebox, etc.), bare metal + several RTOS; networks (everything from obscure Ethernet variants over IP networking to REST APIs), fieldbuses, and internal buses (PCIe, SPI, I2C, UART, etc.); relational databases (SQLite, MySQL, PostgreSQL); engineering and project management according to medical device standards (FDA and ISO/IEC);
Résumé/CV: Full résumé available upon request
Email: [email protected]
Hello, I am Johannes Agricola, a software engineering consultant based in Germany (GMT + 1), but available worldwide.The previous decade of my career was mostly focused on embedded software and digital electrical design. I have had particular success implementing medical device electronics and software. I have guided this development through the hoops set by FDA and international medical device standards both as an engineer and a team lead.
I am:
- currently looking for freelance contracts,
- quickly picking up on new contexts and generally able to productively contribute to most projects on day one,
- open to both short and long term involvements.
I am in particular also available for short-term support for teams needing to meet tight deadlines.
http://kamiokanne.uni-goettingen.de/gb/kamiokanne.htm
The FTL muons produce Cherenkov radiation in the water in the coffee cans, which is picked up by the PMTs.
Using this setup gives a much higher rate, as the surface is much larger compared to geiger tubes. Thus it's possible to quickly capture a sufficient amount of muons.
It'd be one thing, if it were just apps. But all of these apps are essentially just containers for some web application.
Do you get access to the web application without the app? No.
So what's the point of the apps? So they can send you notifications and annoy you with irrelevant updates concerning other groups at the same daycare all day long, because they don't care to filter?
If you rewrite DNS, you should of course also have a custom CA trusted by your container engine as well as appropriate certificates and host configurations for your registry.
You'll always need to take these steps if you want to go the rewrite-DNS path for isolation from external services because some proprietary tool forces you to use those services.
Now we're probably just waiting for a law mandating encryption of cloud data. Let's see whether Apple will actually leave the UK market altogether or introduce a backdoor.
However, if you are using docker's registry without authentication and you don't want to go through the effort of adding the credentials you already have, you are essentially relying on a free service for production already, which may be pulled any time without prior notice. You are already taking the risk of a production outage. Now it's just formalized that your limit is 10 pulls per IP per hour. I don't really get how this can shift your evaluation from using (and paying for) docker's registry to paying for your own registry. It seems orthogonal to the evaluation itself.
> Wer in Beziehung auf einen anderen eine Tatsache behauptet oder verbreitet, welche denselben verächtlich zu machen oder in der öffentlichen Meinung herabzuwürdigen geeignet ist, wird, wenn nicht diese Tatsache erweislich wahr ist, mit Freiheitsstrafe bis zu einem Jahr oder mit Geldstrafe und, wenn die Tat öffentlich, in einer Versammlung oder durch Verbreiten eines Inhalts (§ 11 Absatz 3) begangen ist, mit Freiheitsstrafe bis zu zwei Jahren oder mit Geldstrafe bestraft.
I'll just translate the important condition for being punished for defamation ("Üble Nachrede"):
> [...] if not this fact is demonstrably true [...]
I've intentionally kept the somewhat weird word order while translating. It's just as weird to read for a German. It's an old law.
You could try to initiate a video call with the locked device, though.
- Settings / Einstellungen
- Accept / Akzeptierten
- Reject All / Alle Ablehnen
The English translation is on the buttons in the non-translated page and those translations are fine. There's even a reject all button, which is fine too. The only not so nice thing is that the "Accept" button is coloured green.
Again, I don't want to defend those banners.
So, maybe you can exploit it by connecting a camera to the USB port? That would be bad enough. But this code only seems to be called if a video stream is active. So things like unlocking a locked phone seems improbable to be possible.
Can someone elaborate on the naming of that parameter? I would have guessed that a parameter named "cognitive control" yields better cognitive function for larger values. Is there a reason for that name?
As mentioned, this is the first case and can be achieved by calls to sleep/Sleep/etc. You'd only regularly query if there is actual useful work to be done. That's the premise of the second case you quoted from.
The simple case is just putting a thread to sleep for a given time. It's somewhat odd that there's no portable API for that, granted. At least POSIX has sleep and usleep.
The second case is that a thread wants to continue processing until a timer has passed. This has to happen cooperatively one way or another, so setting a timer is equivalent to regularly querying the system time and comparing to a limit. There is simply no need for a "timer" operating system facility. (Even if you were to plug POSIX timers in here, you'd in all likelihood still need to check some flag set in the signal handler in the processing thread. And then you'd still need to check the system time as signals can originate from anywhere, just as with sleep/usleep above.)
In the third case, a thread waits for I/O. Then, of course, the call to that I/O facility defines how any timer is handled. As these facilities are not portable, timers aren't portable. The author refers to this realization as the need to implement "Userspace timers". These are just an artifact of the I/O facility and calls querying the system time, though.
So, ultimately, not having portable timers is the least of our problems. So long as we don't unify select, poll, kqueue, io_uring and what not, we don't have a need for them. And, as the author realized, libraries like libuv, which do an acceptable job at unifying those facilities, tend to provide a portable timer API.
What exactly are you planning to do? OpenWrt is quite flexible. There's this https://openwrt.org/toh/buyerguide.
> Can you do mesh networks?
Yes. Note also https://openwisp.org/ if you want to do a whole fleet of OpenWrt routers.
I didn't see the author at first. However, immediately after seeing the code I checked for the author, because I was sure it was Stroustrup.
For example, I have objections to rustfmt's default style. I would never start discussions on rust projects about changing that to another formatter or changing its configuration. I definitely would carefully ask that people should really use rustfmt, though, if they don't do so yet.