Just add a delay that pads it out the execute time to 10 seconds. O(1) ez.
Just add a delay that pads it out the execute time to 10 seconds. O(1) ez.
I reserve .elf for executables for other platforms, like microcontroller firmware.
Na let’s keep timezones, there useful for humans who generally want time to mean something, but lets ditch daylight savings time, all it does is make scheduling a massive pain twice a year, and messes up everyone’s sleep cycle. Without it, timezones would just be a fixed offset from another, minimizing trouble.
Don’t forget the loss of productivity in the hours before the meeting, spent worrying about it.
Hot take, C is better then C++. It really just has one unique footgun, pointers, which can be avoided most of the time. C++ has lots of (smart)pointer related footguns, each with their own rules.
Prevent subprocess from killing itself until finished.
Well first off, how nice/tolerant is your management? Do you have savings? Some companies can fire people over this stuff, other will just ignore it.
The easiest (and least likely to make anyone mad) solution would just be to bring in your own machine and use celular internet. This way your setup will be completly seperate from the company network, and they can hardly claim you were exposing them to malware or anything. On the other hand you might have problems accessing devices like printers without copying files back and forth (are USB drives allowed?).
This is actually how you should declare something that you will never change, but something might change externally, like an input pin or status register.
Writing to it might do something completely different or just crash, but you also don’t want the compiler getting creative with reads; You don’t want the compiler optimizing out a check for a button press because the “constant” value is never changed.
I don’t think you could fit video on that microcontroller, even with the best compression. But some low memory and compute video compression for embedded devices would be nice.
I don’t know if writing a custom image compresson program and streaming graphics rendering code with worth saving a few bucks on parts.
I used it in a few microcontroller projects, let me get away with the cheaper 8 bit microcontroller with 64K of flash. The streaming decoding is real nice, because it can be read from flash and sent of to a display, without ever keeping it in ram. (4K!)
GNU is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX is not UNIX[Maximum call stack size exceeded]
Better cat version:🐈(){🐈|🐈&}
Looking at other people’s schematics and messing around with making changes to them is a great way to pick up new tricks, but I recomend you also lean some of the basics. Experimentation is the best way to learn and internalize, so make sure do do plenty of that. I highly recomend you pick up a decent solderless breadboard, assortment of parts, an adjustable lab power suppy, multimeter, and osciloscope. For assembling projects in a more permenent way, I would recomend a perfboard, some thin insulated wire, solder and flux, and a good soldering iron.
Someone who beleaves that they can get out of some or all the obligations using some magic pseudo-legal phrases.
It started as people trying to imitate rich people exploiting legal loopholes, but then some grifter “guru” found them and decided to make a quick buck giving rather bad legal advice. This worked, causing in more grifters getting in, with depressing/hilarious results.
Humans are diploid. We have 2 independent copies of every chromosome in each cell, one from each parent. They function as “backup” copies. If an error is on one, as long as the other one has a good copy of the effected gene, nothing happens. However, if parents are related, it becomes possible to receive two identical (or nearly identical) copies, and lose that backup. In that case, any error/mutations will cause problems.
Unfortunately, this keeps changing. Old slurs get recycled or forgotten, and new words become offensive. Corporate guidelines are often hugely overbroad to avoid offending anyone. The best way to avoid things like what just happened, by checking slang in a dictionary before using it.
Of course there is an xkcd (or rather what if on it)
Computers can really just do two things: copy data and do math. Anytime your your doing anything but copying data verbatim, there is math involved. Anytime your reformating, filtering or acting on data their will be some math involved.
Take displaying an image: you can’t just copy image data to the screen, because it could have a different resolution, or color space, or be compressed. In all of those cases, you will need to do a lot of math to get things to work right.
The exact math varies, in graphics, CAD or geospatial stuff, expect a lot of geometry. Any sort of statistics or classifier is going to involve a lot of linear algebra. Even simply storing data in s quickly accessable manner involves quite a bit of math.