detinho

I can use myself as an example: I have crohn's disease and I can take doses of 50000UI for some weeks, then 4000UI daily and after a year have my Vitamin D results as low as 20ng/ml.

I think parent is saying overcommit with OS threads. 4k requests = 4k OS threads. That would lead to the problems parent is talking about.

Don't know about wget, but curl also provides libcurl [0] so you can embed it on your software. Also curl supports a wider range of protocols, as can be seen on [0].

[0] https://curl.se/libcurl/

Sorry but, what is the mistake on the highlighted sentence? I'm not a native english speaker.

Settings -> Preferences.

[x] Restore previous sessions [x] Unsaved changes [x] Temporary files

But to do that "shittier" would have to get a good implementation and turn on a bad implementation. Formatting might not be enough.

Howerver the main idea is very interesting.

I always try to care about the reviewers. Not too large PRs so they don't LGTM it instantly. Not too small PRs so they don't have to switch contexts multiple times a day or search through many smaller PRs to get context why new PR changes specific lines.

I worked at a startup that had many internal tools for solving small problems using Retool. One frontend guy even added a "diff" component so we could compare json payloads and manually edit them.

I have to admit that it's not the best of the worlds, but for small, focused internal interfaces that call some APIs, it can serve well.

Don't know about this new tool, but talking of retool itself, I also don't see it being used for a full fledged customer facing application.

Also windows 11 keeps enabling windows defender real time protection. This behavior is common on windows: do not respect user preferences.

Well, I'm programming on windows for about 6 months now, comming from using Linux for the last 5 years. I have to admit I was forced as my new notebook BIOS has a wrong VBT configuration and that makes the Linux kernel to not recognize my HDMI port.

And I can acomplish any other task a regular developer can do (and I was doing) programming in Java (with sdkman), using docker containers, git on the command line, Big Data tools (flink, iceberg, haddop, etc) and even some bash scripts (nothing too fancy).

The only things that bothers me are the CRLF x LF and sometimes the windows defender making the fans go crazy, but thats is a minimum and I can do some workarounds, the same way I did with bluetooth and audio on Linux.

If the only thing you need to allocate memory to is your queue, then maybe. Otherwise you'd incur in problems like the sibling comment. That's the very same reason you limit connection pools on applications that connect to a database: to prevent some instance to use all the database server connections and leave nothing to other instances.

What kind of skill does this type of test measures?

I think the main ones are:

* How much about the language the candidate knows. Not the control flow and data types, but how to navigate and where to look for information. And that leads to bellow

* how quickly one can understand a codebase (at least part of it) and start delivering

What else?

If that's one of those "think out loud" tests it's possible to get a clue of how the candidate thinks, but it's not specific of this test.

Maybe some token expired and could not be renewed. They also mentioned a bug on a client grpc library.

Indeed. Recently my wife updated her google account password thinking she was updating the password from the game she wanted to play.

She only knew because I'm on the recovery password list and as soon I received the email from Google asked her to confirm.

Reminded me of a song from Brazilian singer Raul Seixas "O conto do sábio chinês" (a tale about the wise Chinese)[0]. I stopped to actively search about the meaning / sources of many of his songs and let the dots connected naturally.

Today one more line has formed.

[0] https://youtu.be/9Co4ORFSBlQ

There are even companies mottos like "Hire talent over experience until it hurts" which contributes to said desperation when you first hear it.

I guess to get 5 seconds back it would have to many many "green success" or "red failure". Then a slow network hop would get the 5 seconds back.

Specially when the ide doesn't use standard names and/or introduces new terms. Visual/ide tools to use git are welcome and I use them occasionally. But the cli should be the common denominator.

For what I see from the discution it seems to be more a practical decision to not use real time resources and techniques for much higher times. So 1 day for example would be a waste of development time to try to use real time, you could use alerts and background jobs to fix issues. But when you reach shorter and shorter timeframes and bad things can happen a real time approach starts to make more sense.

Now, some parent comment mentioned RTOS. Maybe for a real time OS there would be a practical hard upper bound. But for real time systems in general this upper bound would be totally domain specific.

I'm probably wrong, but isn't real time not about how fast you can react but if you can react on a defined time constraint? Or is there a time threshold you can't consider real time any more like 1 day? Edit: just like you said, 10ms, 1s, etc.

In the long run "small" improvements adds up. The margin will never beat time.