I recommend having a public portfolio. You needn't have all your hobby code be public, but I think having source you've written available is an advantage.
When I was doing interviews, I definitely looked at GitHub (etc.) profiles of they were listed on the resume. I even found at least one indirectly -- either from their email or LinkedIn.
I like to point people at my accepted patched to open source software (Git and a Haskell library).
Multiple hour-long interviews I'm actually fine with. It's not ideal, but in that case at least the company is also spending resources on the process.
Homework / pre-interview projects that take more than a hour is unreasonable, to me. I have public repositories / commits I can share with you if you want to see how I write code.
Yeah, I ghosted at least one company because the pre-interview task was far too much effort. I'm all for having some writing of code as part of the process, though IME reading code is much more frequent/important.
I guess we all set our own limits, but I refuse to work more than an hour or two without (at least an expectation of) pay. Maybe that's privilege talking, tho.
Most people might say Haskell '98, but don't really mean it, because they don't want n+k patterns, and do want hierarchical modules.
Also, the FFI is simultaneously incredibly useful and a new level/kind of unsafety that doesn't exist in "pure" '98. And, with most Haskell programs still being native (not in-browser, or JVM, or CLR, or other VM), I think the FFI might be undervalued for it's frequency of use.
An InstantPot (or other pressure cooker) can cut that time down quite a bit. I set mine on 40 minutes, but it takes a little while to get up to temp/pressure at the start and at least 15 minutes to slow/natural release the pressure at the end.
Still, dry beans to food in about an hour is great! Also much easier to control your sodium intake, it that's a concern.
Love?
If you can find it https://www.imdb.com/title/tt1228865 is a good watch. It covers other methods, but it becomes clear how fast, effective, and painless nitrogen asphyxiation can be, as the presenter has to receive assistance in order not to die while attempting to get close to the experience (without dying).
It's also a bit sad, as it makes it clear that for at least some capital punishment advocates, suffering is a desired part of the outcome.
I'd like to avoid death, but I can foresee a potential future when my quality of life is negative and no amount of volunteer effort can bring it positive. If that happens, I'd like to opt-in to mortality via inert gas (probably nitrogen) asphyxiation.
If we must have capital punishment, inert gas asphyxiation seems to be the best known way to do it. I'm not convinced we must have capital punishment, tho.
Right now? Probably.
In the past, definitely: https://techcrunch.com/2022/09/29/amnesty-report-facebook-rohingya-reparations/
Great comment. I can't figure out which "one" you are talking about, because I find Facebook/Meta oppressive.
https://hachyderm.io/@BoydStephenSmithJr/111535813328842924 (This might be a duplicate, but I'm not seeing it, on my instance, yet.)
Question (not mine) here: https://functional.cafe/@hungryjoe/111433769863600613
I think I answered it well over there. But, posting to encourage activity.
This is inconsistent with the preservation of democracy, as it allows a third party to confirm exactly who you voted for, and reimburse or punish you for it.
Mainly you'll have to tweak point 3, to use existing E2E.verified voting approaches which are only tangentially related to asymmetric encryption (and private keys).
We might use asymmetric encryption and private keys for some parts of identity verification, but you wouldn't sign your ballot with it.