Here's what I look for with software engineers II hire.
Pragmatism: pick the right solution for the right problem. And your work should create minimal work for others.
Thirst to learn: there is always something new and exciting and there's always a better way to do it. Look for that. It also means being open to feedback.
Collaboration instead of execution: I need my team to challenge me. For that, they need to get as much of the bigger picture as they can. That means always being able to answer "why" you do things. It also means that I expect healthy conflict with my teams. If you go from being taught to teaching me, you immediately get a bump in my list of top teammates.
No excuse: we acknowledge problems and deal with them together. (Requires a good work environment though).
As you can see, nothing I wrote is purely code related. Only thing I ask tech wise is: know your shit, where to find it, who to ask.
Also, my top resource to get people started with what it means to become a software engineer is solidbook.io.
Nope, it's not even the season pass. I was giving such examples regarding the whales who want to look cool, but in reality others often only see the default skin if it's from past season.
The 60$ skin is their pay to play roulette to get a 1% to get said skin with increasing price to get next "prize"
Maps, warframes, weapons and skins will also likely be loaded as needed, so you'll probably start with 20GB but bloat to 60 as you play
Another trick I noticed playing CoD mobile is that they don't load every other player's skin, only the latest. So if your install doesn't have it, it only display's the default skin for other players. Which also mean that the skin you paid 60$ for in the last Season Pass is only visible by a few players.
I started learning programming concepts as a teen by using RPG Maker. It introduced me to concepts such as variables, conditions, loops in a "low code" environment.
Thing is, I had a reachable goal which made it easier for me to learn and feel good as I had a tangible result. Things such as "I want to add a point everytime I touch X item" where very good for this.
IMO, I wouldn't worry too much about the language at first and focus on small reachable goals you want to achieve. But to each his own way of learning.
Like games? You should probably check out GDevelop.
Want to automate some of your online tasks? Maybe n8n.io.
Also, it's better if the tool you use starts with a high level of abstraction (it's very esay to use) and allows you to add in some scripts.
If you want to go further, pick a language and go through the basics. And if you're feeling even more adventurous, head to roadmap.sh to find a learning path towards your goal.
Edit: Also, ChatGPT is really good to teach you IF you always ask it to explain whatever you don't fully understand in the code it writes
I'm on tech Twitter and trying to switch to Mastodon. Unfortunately, the latest news and top content are still on Twitter and I don't want to be missing out on either of those.
Sorry but you are using the wrong cloud storage provider.
I've switched to pCloud on black Friday. It was a one time payment for 2TB lifetime (10TB is also available) cloud storage. I checked and it was ~250€ at the time.
Considering the amount of HDD I've burned through in the early years I've already saved a couple thousand dollars and I haven't lost any file since.
Just make sure to watch their price as they currently have a sale and I don't believe for 1 second that the initial price was in fact 1140€ for 2TB as advertised.
Here's what I look for with software engineers II hire.
Pragmatism: pick the right solution for the right problem. And your work should create minimal work for others.
Thirst to learn: there is always something new and exciting and there's always a better way to do it. Look for that. It also means being open to feedback.
Collaboration instead of execution: I need my team to challenge me. For that, they need to get as much of the bigger picture as they can. That means always being able to answer "why" you do things. It also means that I expect healthy conflict with my teams. If you go from being taught to teaching me, you immediately get a bump in my list of top teammates.
No excuse: we acknowledge problems and deal with them together. (Requires a good work environment though).
As you can see, nothing I wrote is purely code related. Only thing I ask tech wise is: know your shit, where to find it, who to ask.
Also, my top resource to get people started with what it means to become a software engineer is solidbook.io.