> Why is it acceptable for front end code to be of lower quality than the rest?
While I don't think that f/end should be of a lower quality than the rest of the stack, I also think that:
1. f/end gets the most churn (i.e. rewritten), so it's kinda pointless if you're spending an extra $FOO months for a quality output when it is going to be significantly rewritten in ($FOO * 2) months.
2. It really is more fault tolerant - an error in the backend stack could lead to widespread data corruption. An error on the f/end results in, typically, misaligned elements that are hard to see/find.
Far from making me fear for my job, LLMs have me more confident than ever that I'll always be able to find some kind of paying programming work, even if it's all short-term contracts (as I get even older).
I bought my first house for 650k (Brisbane) just before covid. It’s now worth about 1M. 350k appreciation in ~4 years - bonkers. Glad I got it then since I probably wouldn’t be able to buy it now.
You can still get a place in the 700k area but it’s a lot further out, a lot older and will likely need a lot more work. That said many in our generation inherited the boomer attitude of big house and big backyard - I think expectations need to change, but negative gearing really needs to go.
I made a few courses on Udemy and wrote a book, over a few years net about 20k, super cool! Relative to how much time went into it I probably didn’t actually make that much money but I had a great time and it feels fantastic to make some money on my own initiative
I would not get too concerned about AI entirely replacing you - focus on getting a job and learning how to code without just asking ChatGPT for code and copy pasting it blindly. You should definitely use AI tools, but only to help you learn or to do something you already know faster, not as a crutch.
ChatGPT and friends is definitely a good tool to get snippets, like Stack Overflow, just make sure to understand what you get, just don't copy / paste blindly.
You could try Cypress, it has a component testing solution. It's not for everyone, but the way Cypress works, is it will auto-wait for your assertion to run, so you don't need the whole async/await.
No solution is perfect! I see this as more integration / component testing than a true unit test.
I have majorly had this issue since having kids particularly.
I couldn’t cope, so after a lot of soul searching, I found I just had to de prioritize things. I accepted there are some things I’d love to do but just aren’t as important, high enough ROI, etc. Hard pill to swallow.
I have thought about it - I talked to many of my friends in trades. They are all jealous of how good I have it. Most of them are earning ~70% of what I do, often spend ~2 hours commuting, hard on the body, risk of injuries... maybe you can transition to a orthogonal field in software to change things up?
From exploring this segment for a while, I believe that dictation software is the "brick" in the hair-on-fire analogy (hence, it provides some relief, but is far from an actual solution). There is a form of water (scribes on retainer) but it is too expensive for all but the most profitable of specialties. The problem to be solved is not "dictation but better," but "take this cognitive load away from doctors, and keep notes accurate." (which is what scribes with experience do.) In a broader sense, the problem to be solved is the American healthcare/insurance system (the reason these notes have to be taken in this way in the first place)...
> Less time spent taking notes == more time with patient.
This can be true in some cases, but from what I understand, industry wide it would end up more like:
Less time spent taking notes == more patients scheduled.
Which is still of value, but fails to solve the original point of a physician's frustration, and possibly makes it worse (assuming the physician is still the one generating, handling and verifying the notes, but with better efficiency).
