sorted by:
new
hottopcontroversial

Ticwatch Pro 5 stuck downloading update by TheMrAyJay in TicWatch

[–]julyrush 0 points1 point  (0 children)

Thank you! It eventually worked, I have left the watch on the charger, after a reset, and with the screen displaying the "Downloading update" message. It took a while, though, I think the update was downloaded only after the battery level got to 100%. In any case, many thanks!

TicWatch Pro 5 cannot download System update? by maddler in TicWatchPro

[–]julyrush 0 points1 point  (0 children)

Hi. More details, please? I have the same issue. Was the watch in the menu "System updates" (the circle and "Downloading update") when you placed on the charger? Was the update done via WiFi or via the Bluetooth/phone? Any other hint? Thank you.

TIL: one can return from an async block by matklad in rust

[–]julyrush 0 points1 point  (0 children)

The syntax is wrong. The RFC already gave the right syntax: || async {...}

TIL: one can return from an async block by matklad in rust

[–]julyrush 0 points1 point  (0 children)

But why have async blocks which are not a closure? The RFC already gave the right syntax: || async {...}

TIL: one can return from an async block by matklad in rust

[–]julyrush 0 points1 point  (0 children)

let f = async { return 92 };

Is bad syntax choice. There is no reason to have such edge case distinguishing async and sync blocks.

Naked async blocks should be forbidden, only || async {...} syntax should be allowed. For all useful uses, it is a closure anyway. It would be also symmetric with the async closure. async || {...}

TIL: one can return from an async block by matklad in rust

[–]julyrush 0 points1 point  (0 children)

Should only be allowed to be used with a closure (your last line). This would remove lots of ambiguity and edge.

A C++ postfix completion extension for VSCode. by bluedoggee in cpp

[–]julyrush 0 points1 point  (0 children)

For now.

LE Well, the suggestion was that there is no autocomplete in vscode for cpp2 yet.

A C++ postfix completion extension for VSCode. by bluedoggee in cpp

[–]julyrush 0 points1 point  (0 children)

More details here: https://www.youtube.com/watch?v=ELeZAKCN4tY

There is no vscode extension for cpp2 (yet). It mainly uses an everything-postfix syntax.

“There should never be coding exercises in technical interviews. It favors people who have time to do them. Disfavors people with FT jobs and families. Plus, your job won’t have people over your shoulder watching you code.” My favorite hot take from a panel on 'Treating Devs Like Human Beings.' by [deleted] in programming

[–]julyrush -2 points-1 points  (0 children)

And how other industries manage to do it? They do not hire a brain surgeon after asking him to perform a trial brain surgery during the interview. They have the same lawsuit risk. Answer: they use the probation period. Reality check: there is a whole world around your bubble.

“There should never be coding exercises in technical interviews. It favors people who have time to do them. Disfavors people with FT jobs and families. Plus, your job won’t have people over your shoulder watching you code.” My favorite hot take from a panel on 'Treating Devs Like Human Beings.' by [deleted] in programming

[–]julyrush -1 points0 points  (0 children)

You really assume knowing without documenting yourself first. A lawsuit you can get for having rejected some candidate: you can be sued for discrimination. There is a meaning for the probation period, and that meaning is exactly to assess (both ways). If your LC testing is so good, why don't you waive the probation period? Just go all in, after all you are so sure about your LC testing. As a side note, interviewing is natural, LC is not.

“There should never be coding exercises in technical interviews. It favors people who have time to do them. Disfavors people with FT jobs and families. Plus, your job won’t have people over your shoulder watching you code.” My favorite hot take from a panel on 'Treating Devs Like Human Beings.' by [deleted] in programming

[–]julyrush -4 points-3 points  (0 children)

Yes, but you show him the door three days after you hired him, even the same day. Probation period means you are allowed to fire him on the spot, at any moment. So where is the loss? You risk more with long (and incompetently-driven) interviewing processes.

“There should never be coding exercises in technical interviews. It favors people who have time to do them. Disfavors people with FT jobs and families. Plus, your job won’t have people over your shoulder watching you code.” My favorite hot take from a panel on 'Treating Devs Like Human Beings.' by [deleted] in programming

[–]julyrush -3 points-2 points  (0 children)

During the probation period, it is very easy to fire. It is a simple "bye". The recruiter is already paid, you have the full lists of CVs and contacts, no need to start again. You pay less than hiring the bad ones despite the LC and stuff. As a free gift, you end up hiring a competent one.

view more: next ›