The BEST Way To Become A Software Engineer 

Well...?

R they?

And ..?

I became curious instead of laughing

Are they?

Absolutely correct 💯

what would be the essential books? especially as a Business Analyst such as using Python

It depends a lot on your current level and what your requirenents are. I quite like ”Hands-On Machine Learning with Scikit-Learn, Keras, and Tensorflow”. It has a mix of some data wrangling with dataframes, visualization and some analysis with a practical emphasis. Its at a relatively beginner friendly/internediate level. Its quite useful even if your goal is not doing ML. ”Matplotlib for Python Developers” is quite good for visualization. For more software, and less analysis focus, to develop your Python skills you may like: ”Python Design Patterns: A Step-by-Step Guide”.

especialy if you can find one in your own language that helps so much

I don't think reading books makes a difference. Information is Information. Using your critical thinking, testing and experimenting with what you've learned builds the intuition.

Always learn on the job.

I got the job before getting good at leetcode, need to practice for the next job

@nicholaskipchumba9189 I'm attempting the same transition right now. Was Leetcode all you used to start learning before you landed your first job? If there were other resources you used (or any general advice you could give), could you please share it with us?

I am a civil engineer looking for a transition how should I convince hr or company and what skills are required for transition.

saved me 12:44 minutes, thanks

i DON'T EVEN KNOW what i'm passionate about to check whether they have A TECH PROBLEM

This is more or less exactly what I did. I spent 10 years on steps 0-2 because it never crossed my mind I could work as a developer. Then 5 years ago I started going to meetup events to get to know other programmers with the same interests. I showed off what I made to someone and they invited me to come work for them. It occurred to me later that those events were actually for networking.

this

@@astrolemonade349 You could've just googled the article...

Word

it depends dude, just coz ur experience with a formal background was a good one does not mean other share that same sentiment. its extremely variable & in my case, ive learnt more about programming thru my own self experimentation & grind, so much so the kids in my class call me a "genius" when i come up with a solution to a problem that even the lecturer did not think about. in reality i just grinded my ass off for years alone & it paid off.

While the pacing was slow I bet there were many people as part of your class who were "damn, I already know that stuff, let me go faster please".

I full agree. I was self-taught in high school through gamedev projects + motivation, but formal education was still very helpful. It exposed me to other programming paradigms (functional, declarative), and languages in general (gamedev was 100% C++). It exposed me to other programming problem spaces: XSLT, database, networking, and systems programming. While 85% of my core capability on the job for 14 years was self taught, that remaining 15% slowly picked up in college was very broad and is highly valuable because it's what allows me to pick up any programming industry job and know that I've probably already seen the core difficult problems. Only the surface level problems will be new, as they would to almost anybody who isn't directly knowledgable. When you're limited to looking at someone's value in one team, it can be hard to distinguish who learned slowly, and who learned and applied things "quickly." Those who applied knowledge quickly will quickly be unable to solve more difficult problems because they fail to learned and are barely able to identify the difficult problem at hand. Those who learned a lot of things slowly will comfortably move to different surface level frameworks, languages, or libraries as needed whereas those who don't really have the underlying knowledge will be far less comfortable with this.

For me, the community factor was extremely important. I wouldn't be able to study half as much had I not been in contact with other high performance students, and of course inspiring professors, every single day.

I need to do this lol

i can't understand the tutorial hell thing, i just installed linux and automated my way to do things

Can you link me the video?

That reminded me about reading physics books. Specifically for the rigorous books about theoretical physics, people always said that those books are not for learning the material as a noob. But when you already understand the material, you can read it and really appreciate how well written the book was lmao

do you have a link of that video?

This. Following tutorials without modifying and building just leaves one feeling lost when they actually try to build something. And painter can only get better at painting by painting a lot. The same can be said about programming.

its not about attention span or tutorials and courses, its about how much time chat GPT saves you. I could google my way through a problem, and yeah ill find it eventually... after checking 5-10 links that lead me down rabbit holes that dont do anything. OR i could go to GPT, describe my problem, and it will find a solution in a minute, and if its wrong, ask for another one. I think this is where people go wrong though, like in the video, dont take the steps at word value, you have an infinite source of knowledge that gave you these steps, if in any of them you have a question about what it used or something youve never seen before, literally just ask gpt and it will tell you. now not only are you going through rabbit holes, but now you are going through them with it actually being relevant to your problem, and now you've learned so much about stuff you didn't before. Another thing, NEVER copy paste anything gpt gives you, type it out. learn by doing, not seeing.

can you give an example ?

Yeh, in my opinion/experience tutorial is the best way to get introduced to a subject and see how people organize code and files. Unless you have a mentor your code is gonna look messy otherwise and well you know some things exist. But then again, it is just an introduction, we gotta take it for ourselves to learn about why it works that way and try to edit the given code and experiment further by adding our own ideas

The 10k hours was some bullshit malcolm gladwell spewed out in a biook

**** stack overflow

That's the way I've not started Rust yet. The language looks fun, but the hype was too high.

skill issue

Data structures, memory management, etc. Higher level languages are great for getting things done quickly, but imo they dont allow the programmer to dig deeper and uncover the inner workings of what the computer is actually doing.

You're missing a systematic, comprehensive knowledge and instead getting mythical thinking. If you don't know how things work and how everything is connected you're only capable of cargo cult programming.

Not missing anything. Dont listen to the malloc bros