vaalla

Already exist, it’s called hdr and almost all modern camera supports them. But they take more time.

10 Seniors in east europe.

I manage to break 2 usb conectors in 1 year.

Same for me.

Drivers from 3rd party. Didn’t work on phone development, but was part of a company that developed setup boxes.

We will get a kernel from broadcom with all the necessary drivers that was tested for that configuration. Updating was very hard without support and might cost a lot.

They had a lot of excellent scientists.

Fun fact, the math behind radar stealth was developed by a Russian scientists and was ignored in URSS because it had a shit title. US delayed translating it because they didn’t undersrand the title. After a few years somebody at lockeed marting found it and realized what it meant. I think F-117 was developed based on that.

Probably its just a snapshot at some point, with maybe downloading new stuff when its published. At least thisbis how i’d do it.

I mostly write rust now, but this workflow was finetuned over years. Use 2 terminals each on a diferent monitor, one runs neovim and the other is for building/running. If the project is a bit more complex, I will run it in a docker container( maybe mount the /etc/shadow and frieds so all artefacts are created using the same user as in the outside) . Developed a bunch of tools over the years to optimise this:

• a ‘package manager’ in bash so I have a folder for each project/context. One for work, one common, one for the server stuff like this. All are in PATH.
• parterm - remote control for the terminal so i can start a build from neovim in a different terminal.
• ‘ndock’ - at work I use a bunch of branches, this script will set up a few envs and then start a docker in a folder coresponding to that branch.

At my old job had to work on a remote vm so I setup sshfs for a while, but was slow and just moved all my tools there.

I have a pattern where i put all my projects in ~/dev/<project><branch> and all info related to a task in ~/dev/<project>/bugs/<issue_nr>. This is usefull because I can have scripts the work similar for different projects with small changes. For example to run my binary with the config for a issue i just do

ndock <branch>
nr <issue nr>

This will start docker or connect to an existing one for that branch if available, compile the code, run my binary with the config present in the bug folder. In the last few month started running it with rr to be sure i can debug any random issue.