I've been thinking something similar. Then I thought about all the people who get up early to do construction work etc - fixing things day by day without worrying about fomo or time wasted. That though made me calm and feel that things are ok...
There are reports of blurry text on monitors with resolutions around 1440p or less than UHD. macOS doesn't always scale fonts optimally on these, which can make coding feel straining over time. My recommendation is to look into a 4k or higher monitor for sharper text rendering on macOS, even on a smaller screen size.
I find that Jonathan Blow ranting about Rust game development here https://www.youtube.com/watch?v=4t1K66dMhWk. He adds interesting perspectives to the discussio, how the language makes the Rust game developer resort to arrays and their so called Rust point of views.
People will perhaps not be used to using JIRA and have no idea about processes like Scrum sprints and the purposes of demos and retrospectives. They could try to micromanage your work and make top down decisions with little autonomy and set your deadlines without asking you first. I would suggest you try to educate them about development best practices including some degree of freedom/trust for developer teams and the value of feedback loops and some involvement from the business and good requirements.
While I agree that LLMs can be useful for coders, and productivity can be increased, coding blindly based on ChatGPT code without understanding concepts could result in very serious bugs.
How can you be sure that the code does not have vulnerabilities for example, or solve things in a non-idiomatic way, if you just copy paste code without an understanding.
As long as an understanding of the domain and problem is required a skilled person is required between the codebase and the LLM.
Even if we get to a point in the future where a programmer can be replaced by an LLM, we'll have businesses where they want someone to use the LLMs to create software.
Don't give up! The job market is tough, but I'm sure there are jobs out there that would be a good fit for you. For example, check LinkedIn for job postings. It's just much harder to land a job these days, but I think it's temporary until companies realize they need to hire again.
Some tips: Reach out to recruiters who have contacted you in the past. Sign up for online CV databases. Use your network and contact former colleagues to see if their companies are hiring. Work on a side project that excites you and makes you proud to change your mindset, or take an online course. Try to get excited about the challenge instead of thinking about giving up. I just watched a YCombinator video which, among other things, talks about not giving up too soon: https://youtu.be/al-15mMAS18.
Also, try to get feedback when you're rejected. Are you showing genuine interest in the job? Do you ask insightful questions, and do you submit take-home assignments without bugs?
Rust is still lacking good GUI libraries and C++ and there are lots of libraries out there written in C++. Rust is more up and coming. That said in my opinion Rust is a nicer and better language since you get cargo and a modern safe efficient language. In my opinion Cargo is great and CMake and similar tools for C++ are not nearly as nice.
I feel the same way about Spotify. It reminds me of Netflix in that it's hard for me to find interesting content to consume. I wish there was a way to become a power user, enabling me to better organize my audio library and delve deeper into their extensive collection to uncover new, intriguing music.
Moreover, the fact that artists seem to be paid so little makes me increasingly inclined to consider leaving their service for something else, like Tidal, or simply using YouTube Music.
By the way, if anyone is working on a Spotify killer, feel free to reach out. It would be fun to help out.
Other chess apps have the mouse approximately in the center of the piece so that when you drop the piece it's dropped where the piece and the mouse is located. I've accidentally dropped the pieces on the wrong squares on this page, since the mouse is to the right of the piece.