232 karma · joined January 10, 2021
That's probably more simple than you'd want to hear, but there is no such thing as "best". If you search for the best in anything, you can find tons of posts/articles/whatever all suggesting different tools are the best. That's the beauty of the internet. You'll always find something to substantiate your assumptions, or in this case make you doubt them.
I can only speak to your music production ambition, but I've spent way to much time looking for the best DAW, compressor/effect/synth plugin, best hardware. All those things are distractions. See which ones are popular and available for your platform and pick one. Learn to produce music first, it doesn't matter what tool you do that in, if a year from now you end up deciding you don't like your tool you can still change it. Its like worrying about which language to program in without even being able to write simple programs. Just pick one.
I don't know about the legalities, but it may well be that banks have little choice but to comply versus going against the regulator. Though Barclays' line about "we want to protect your money" is a bit much.
Personally 9 hours per day wouldn't work, after a solid day of programming I tend to loose focus too much after about 7 hours, but some of the alternatives work fine.
Can share that experience as well, my first job there were 2 devs who were great programmers, highly educated. At every chance I tried to get as much knowledge from them as possible. They were happy to share and equally happy when they saw me improving.
You can definitely be a PM, most I know have no coding experience. Its an entirely different skillset. Maybe not a PM but a PO or management role if that suits you more. If it helps, my current manager realised after a few years of coding that he'd never be a great programmer (whatever that means to you) and went into management. Turns out helping other people be great programmers is a lot more satisfying to him and the background in programming is a huge asset for him. If you are a PM and you have more than just a superficial knowledge of programming, that is a huge asset.
As far as coding, I have nowhere near your years of experience, but focusing mostly on quality, clean code and really learning how to do stuff like write meaningful tests really helped me. Read Clean Code and A Philosophy of Software Design. Go find some people at your company who clearly have no issue with these things and pick their brains.
I don't think you're lost, just not sure about what you want to do with the rest of your years. Take a break and figure that out. You're clearly willing to learn so if its better coding, go learn, if not go do something else.
For example, I work in front-end but I do most interviews across front-end, back-end, devops, always together with someone who's familiar with the domain or the specific stack we're recruiting for. In that case I'm there to test more on softer skills, but also its a good test to see if a candidate can discuss their domain with someone who isn't familiar with it.
Sure you won't pick up a language from mostly just hearing it like when you were a little Hans but you'd be surprised what you can learn when you're not "young" anymore, whatever "young" means.
- Make a plan, when are you starting, what do you want to have accomplished in year 1, 2, 3. Commit to it.
- Make a financial plan, I basically lost 65% of my income (ouch), but I knew there were high paying jobs out there. How long can you live on a lower salary or are you good just taking a cut anyway. Do you need to take time off to retrain? What will that cost. For me budgeting that all out really helped.
- Figure out your worst case, for me it was "what if I can't get a job" or "what if I do and after 6 months I hate programming professionally". Can you still get back to your old career, do you want to?
- What skills carry over, do you have some business or commercial experience? Or some background in a field where those skills would help being a programmer?
- Learn your butt off. I've been doing this for 3 years professionally now and I spend most evenings 50/50 coding on pet projects and reading literature/CS books. Its hard but I've managed to make back my lost income and somewhat compensate for the lack of actual programming years. Its also been rough on my social life, but that's the price for me. I figure once I hit the 4/5 year mark I can maybe take a breather. This year though with corona it actually works out fine, nothing better to do anyway.
I don't pirate these days, because paying a few bucks for a movie rental isn't that much to me, but availability is still a problem. For awhile Netflix seemed to be a solution but now there are so many streaming services that "Hey, lets watch movie X" can be cumbersome. Wouldn't be the first time that only some service has it that I can't see in my region.
I see people using .filter(Boolean) a lot for example. If the signature of that were to change, for sure it wouldn't be something that quietly gets implemented, but I wouldn't pass formatting functions to these operations carelessly, especially in a codebase where there may not be tests. Some of the safer ways I've seen are use of unary helper functions to wrap the callback, or having the callback actually take the arguments but discarding them like (element, _index, _array). At least that way you communicate some intent.
I enjoy TS and for web applications I wouldn't want to do without it, but it for sure isn't the "end all" since it still needs to work with those issues. Ultimately though in the case of some of the examples, a type system in a language with optional parameters doesn't excuse you from having to use your brain. Especially if you're the kind of developer who thinks testing your code is just unnecessary.
Your example is clear enough because the signature is simple, but in more complex functions I've found that becomes obscure real fast, particularly if types are then passed down to something which also uses generic types. Enabling people to reason about things is not as clear as actually telling them what it is. If the 2nd of 3 generic types is the return type for whatever reason, call it SomethingReturn type and remove that ambiguity.