Early in life it makes sense to move on more easily, not because we value people or partners less, but because we’re still figuring out ourselves and how the world works. There’s just more uncertainty.
Later, when we know more about who we are and what fits, it’s natural to switch less.
In Poland you can get one without doctors referal (for CT you need one because of ionizing radiation exposure), it cost between 100-200$ in normal, reputable hospital (not one like from the street view).
From my experience ability to turn equivalences to equlities and vice versa is very usefull. Without this you are ending in setoid hell - intracable mess of isomorphism. I suspect that also Higher Inductive Types have lots of potential to simplify practical verification effords (apart from obvious usecases of quotients and truncations)
I am very happy with Elm on frontend. When working with Haskell I tend to generate most of frontend types for Elm directly from haskell with elm-street (https://hackage.haskell.org/package/elm-street)
The downside of Elm simplicity in comparison to haskell is inability to express even simplest typeclases like Ord, or very useful constructions like Lenses.
Dependent types and homotopy type theory for general purpose programming. I am definitely excited about it, but not really sure if those hopes will ever materialize as some useful (even in the limited scope) technology.
Some time ago i discovered, that when I am unable to write code, I am still able to engage in less demanding but still very beneficial activity for my project:
Pair programming with less experienced members of the team. It was very important for me, because previously, when i had "bad day" i was ending with completely wasted day. Now, even when i am not able to do work myself i am still able to boost significantly someones output.
For solo projects, watching advanced tutorials, or conference talks about technology beneficial for current project gives me sense of progress during days when i am unable to code.
I think that this branch of engineering is still in its infancy (like electrical engineering int the times of edison). I am courius how front end development will look when dust will settle, maybe in 50 years?
Maybe todays, heated disucions will be setted for good? Or something new, better will be invented?
If you want to keep this job, but looking for some motivation: Maybe try to focus on developing good (expert level) craftmanship?
If overall quality of project is poor, it maybe even be possible to find some narrow aspect which is possible to polish. Expertise gained that way may be used later, when you finally start working on something meaningful in the future.
Visual editor for cubical-agda code, currently I am rewriting it in haskell and integrating with emacs. New version will allow to edit code in 3 and 4 dimensions :)
It does not meant that merit do not play role, simply there is so many highly skilled, and good candidates, that only small percent of them will get the dream job.