There's this trend I've noticed with new developers where

They learn to code, build a few sites and suddenly want to be an entrepreneur. I see that as crazy. You don't have any experience about design systems and architecture and haven't worked on a real job to at least gain a tiny bit of experience so you don't make obvious mistakes.

They build a few sites, I'll admit that some are beautiful and post the links here for us to admire and encourage them. That's ok but what's more important at that level is code reviews, your site may be fine but your code would be poorly written with bad support for maintenance.

They learn about backend, follow a few tutorials though some may do it on their own but suddenly they want to make Facebook. All I can say here is LOL.

They learn to code but do not care about unit testing. The solution is obvious.

They discover optimisation techniques and overuse them. Just as there's premature ejaculation, there's also premature optimisation.

They do a few projects on their laptops and not care about source control. You must learn to use git PERIOD.

They think that getting jobs is easy, no my friends it isn't, sometimes you have to work with a messed up startup that's just as bad as a slave owner just to add years of experience in your resume.

They do not develop their problem solving skills, it's not easy but you can check out hackerrank and try their beginner problems to get acquainted.

They learn their stack superficially, I understand that it's not easy to go deeply in any stack but it's important. There's this interview I had regarding react, they asked questions in a non react way but expect you to respond in a react way. Some answers included Context API, Refs and design patterns.

They just stop at writing code. You should always try to be better than yesterday. Check out the SOLID principles and try to apply them to your projects, it'll make life easier for you especially during interviews and code maintenance.

The summary is know your level, develop a plan to improve and implement the plan. Never ever think you have arrived.

My advice is that try not to do these things.

Senior Devs in the community can contribute and I can update the list.

Walai op you have said it all. Its why I recommend people to get into jobs early. There's so many things you can never learn on your own except you start working. I used to feel on top of the world with my toy projects in my room but men when I started working I saw that I didn't know anything. There's so many hidden secrets you don't see in documentations and on stack overflow.

tensazangetsu20:
Walai op you have said it all. Its why I recommend people to get into jobs early. There's so many things you can never learn on your own except you start working. I used to feel on top of the world with my toy projects in my room but men when I started working I saw that I didn't know anything. There's so many hidden secrets you don't see in documentations and on stack overflow.

I think I need to start applying for jobs now.

pman06:


I think I need to start applying for jobs now.

Better start getting a job is a job on its own which unfortunately so many people don't take serious. They apply to just ten jobs and start crying that there's no jobs lol

tensazangetsu20:

Better start getting a job is a job on its own which unfortunately so many people don't take serious. They apply to just ten jobs and start crying that there's no jobs lol

valzey:
There's this trend I've noticed with new developers where

They learn to code, build a few sites and suddenly want to be an entrepreneur. I see that as crazy. You don't have any experience about design systems and architecture and haven't worked on a real job to at least gain a tiny bit of experience so you don't make obvious mistakes.

They build a few sites, I'll admit that some are beautiful and post the links here for us to admire and encourage them. That's ok but what's more important at that level is code reviews, your site may be fine but your code would be poorly written with bad support for maintenance.

They learn about backend, follow a few tutorials though some may do it on their own but suddenly they want to make Facebook. All I can say here is LOL.

They learn to code but do not care about unit testing. The solution is obvious.

They discover optimisation techniques and overuse them. Just as there's premature ejaculation, there's also premature optimisation.

They do a few projects on their laptops and not care about source control. You must learn to use git PERIOD.

They think that getting jobs is easy, no my friends it isn't, sometimes you have to work with a messed up startup that's just as bad as a slave owner just to add years of experience in your resume.

They do not develop their problem solving skills, it's not easy but you can check out hackerrank and try their beginner problems to get acquainted.

They learn their stack superficially, I understand that it's not easy to go deeply in any stack but it's important. There's this interview I had regarding react, they asked questions in a non react way but expect you to respond in a react way. Some answers included Context API, Refs and design patterns.

They just stop at writing code. You should always try to be better than yesterday. Check out the SOLID principles and try to apply them to your projects, it'll make life easier for you especially during interviews and code maintenance.

The summary is know your level, develop a plan to improve and implement the plan. Never ever think you have arrived.

My advice is that try not to do these things.

Senior Devs in the community can contribute and I can update the list.

I guess Zuckerberg was a senior developer when he wrote the earliest version of havard connection, or page and Sergey when they wrote their search engine

africonn:


I guess Zuckerberg was a senior developer when he wrote the earliest version of havard connection, or page and Sergey when they wrote their search engine

Zuckerberg had been programming for more than ten years before he even got into Harvard and na Harvard he enter o. Sergey brin dropped out of a PhD in computer science to build google. Google was even a PhD project before they decided to make it a business. Those guys were seniors both in practical and academics and as of then no stack overflow or anything to ask any questions. Pure super coding. JavaScript was just a year old. Most things had to be done in C, C++ and assembly.

tensazangetsu20:

Zuckerberg had been programming for more than ten years before he even got into Harvard and na Harvard he enter o. Sergey brin dropped out of a PhD in computer science to build google. Google was even a PhD project before they decided to make it a business. Those guys were seniors both in practical and academics and as of then no stack overflow or anything to ask any questions. Pure super coding. JavaScript was just a year old. Most things had to be done in C, C++ and assembly.

Well, I wouldn't say every new programmer should start coding the next facebook or Google. But if you've studied computer science and graduated, or knows your stuffs with coding, then building the next FB or Google, shouldn't be a fuss. Design patterns yeah, they can be fundamental in designing a product, but in the end, they are not the product, just a blueprint on how you'd go about developing your software. Even if you don't know any of those patterns, and you create a working product, you sure must have used one of them, even though it's unknown to you.


There are lots of self-taught programmers with high end products, and most just went from learning to building their groundbreaking software. So boss, I'll disagree with that part though.

pman06:


Well, I wouldn't say every new programmer should start coding the next facebook or Google. But if you've studied computer science and graduated, or knows your stuffs with coding, then building the next FB or Google, shouldn't be a fuss. Design patterns yeah, they can be fundamental in designing a product, but in the end, they are not the product, just a blueprint on how you'd go about developing your software. Even if you don't know any of those patterns, and you create a working product, you sure must have used one of them, even though it's unknown to you.


There are lots of self-taught programmers with high end products, and most just went from learning to building their groundbreaking software. So boss, I'll disagree with that part though.

True there's this guy I follow on Twitter levelsio. He has never worked as a Dev. He learnt to code and just started making projects. One of his side projects brings one million USD a year in revenue. Many of this kind of stories exists on indie hacker. There's nothing that can't be done with determination. At the end of it all, everything boils down to the individual.

pman06:


Well, I wouldn't say every new programmer should start coding the next facebook or Google. But if you've studied computer science and graduated, or knows your stuffs with coding, then building the next FB or Google, shouldn't be a fuss. Design patterns yeah, they can be fundamental in designing a product, but in the end, they are not the product, just a blueprint on how you'd go about developing your software. Even if you don't know any of those patterns, and you create a working product, you sure must have used one of them, even though it's unknown to you.

I don't think you understand the importance of system design and architecture. It's fine trying to build a social media app as a personal project, but always keep your mind open for what you don't know. There's difference between an app that 100 persons use and what 100,000 people use. You can't get that knowledge on your own.

I've seen people on this platform saying they can build Facebook. I see that as a sign of ignorance because the person clearly doesn't understand the difference between creating an app on localhost for himself and creating for the world to use.

There are lots of self-taught programmers with high end products, and most just went from learning to building their groundbreaking software. So boss, I'll disagree with that part though.

Can you show any

tensazangetsu20:

True there's this guy I follow on Twitter levelsio. He has never worked as a Dev. He learnt to code and just started making projects. One of his side projects brings one million USD a year in revenue. Many of this kind of stories exists on indie hacker. There's nothing that can't be done with determination. At the end of it all, everything boils down to the individual.

You can show us the project if you have the link.

tensazangetsu20:

True there's this guy I follow on Twitter levelsio. He has never worked as a Dev. He learnt to code and just started making projects. One of his side projects brings one million USD a year in revenue. Many of this kind of stories exists on indie hacker. There's nothing that can't be done with determination. At the end of it all, everything boils down to the individual.

Boss please reply my mention.

valzey:


You can show us the project if you have the link.

Remoteok.io. He also owns nomadlist.

SageX1444:
Boss please reply my mention.

Bros check my past threads. I hate repeating myself everytime.

valzey:


I don't think you understand the importance of system design and architecture. It's fine trying to build a social media app as a personal project, but always keep your mind open for what you don't know. There's difference between an app that 100 persons use and what 100,000 people use. You can't get that knowledge on your own.

I've seen people on this platform saying they can build Facebook. I see that as a sign of ignorance because the person clearly doesn't understand the difference between creating an app on localhost for himself and creating for the world to use.



Can you show any

at some point u would realize that u need to understand what ur codes run on and how to make it highly available to clients with low latency, and that shouldn't not stop someone from creating something, how I wish we could discuss this in length.

Over engineering doesn't solve any problem, the goal should always be to move quick. That's my opinion though.

tensazangetsu20:

Zuckerberg had been programming for more than ten years before he even got into Harvard and na Harvard he enter o. Sergey brin dropped out of a PhD in computer science to build google. Google was even a PhD project before they decided to make it a business. Those guys were seniors both in practical and academics and as of then no stack overflow or anything to ask any questions. Pure super coding. JavaScript was just a year old. Most things had to be done in C, C++ and assembly.

Yeah, he is no noob. But was he a senior dev, what's does dat even means, anyways no p, there is no need to argue but it's not every app that would be used by up to 1k concurrent users not to talk of millions, it's like telling a PHP script dev that wants to do something to learn system designs before building that thing.

africonn:


Yeah, he is no noob. But was he a senior dev, what's does dat even means, anyways no p, there is no need to argue but it's not every app that would be used by up to 1k concurrent users not to talk of millions, it's like telling a PHP script dev that wants to do something to learn system designs before building that thing.

True sha. Everything eventually boils down to the individual Las Las.

There are two types of programmers.

1) The ones who learn frameworks just enough to whip up an application. These ones are standing on the shoulders of the actual engineers because they rely on libraries, APIs and frameworks built by the engineers.


2) The actual software engineers who have a deep grasp of the concepts of algorithms, data structures, system design, architecture, design patterns etc. These ones are the programmer's programmer

Any self-taught programmer ambitious and curious enough, can always go from being the former to attaining the level of the later.

A CS graduate is expected to be an engineer already. He can easily learn frameworks if needed.

Just have a roadmap that shows where you're going and follow through with it. You can be the first guy and start earning some bucks but never ever stop there. Go deeper. Tech is fast changing and what's trending today might be outdated tomorrow. But the core fundamentals never change.

valzey:


I don't think you understand the importance of system design and architecture. It's fine trying to build a social media app as a personal project, but always keep your mind open for what you don't know. There's difference between an app that 100 persons use and what 100,000 people use. You can't get that knowledge on your own.

I've seen people on this platform saying they can build Facebook. I see that as a sign of ignorance because the person clearly doesn't understand the difference between creating an app on localhost for himself and creating for the world to use.

As a first class graduate of computer science, I believe I know more than you think I know, but then again I'll leave it at that.

Have a great day.

Grandlord:
There are two types of programmers.

1) The ones who learn frameworks just enough to whip up an application. These ones are standing on the shoulders of the actual engineers because they rely on libraries, APIs and frameworks built by the engineers.


2) The actual software engineers who have a deep grasp of the concepts of algorithms, data structures, system design, architecture, design patterns etc. These ones are the programmer's programmer

Any self-taught programmer ambitious and curious enough, can always go from being the former to attaining the level of the later.

A CS graduate is expected to be an engineer already. He can easily learn frameworks if needed.

Just have a roadmap that shows where you're going and follow through with it. You can be the first guy and start earning some bucks but never ever stop there. Go deeper. Tech is fast changing and what's trending today might be outdated tomorrow. But the core fundamentals never change.

God bless you.

pman06:



God bless you.

Bless you too bro

Grandlord:
There are two types of programmers.

1) The ones who learn frameworks just enough to whip up an application. These ones are standing on the shoulders of the actual engineers because they rely on libraries, APIs and frameworks built by the engineers.


2) The actual software engineers who have a deep grasp of the concepts of algorithms, data structures, system design, architecture, design patterns etc. These ones are the programmer's programmer

Any self-taught programmer ambitious and curious enough, can always go from being the former to attaining the level of the later.

A CS graduate is expected to be an engineer already. He can easily learn frameworks if needed.

Just have a roadmap that shows where you're going and follow through with it. You can be the first guy and start earning some bucks but never ever stop there. Go deeper. Tech is fast changing and what's trending today might be outdated tomorrow. But the core fundamentals never change.

I like this

tensazangetsu20:

Zuckerberg had been programming for more than ten years before he even got into Harvard and na Harvard he enter o. Sergey brin dropped out of a PhD in computer science to build google. Google was even a PhD project before they decided to make it a business. Those guys were seniors both in practical and academics and as of then no stack overflow or anything to ask any questions. Pure super coding. JavaScript was just a year old. Most things had to be done in C, C++ and assembly.

You’re right, Zuckerberg had elite programming chops but Sergey and Page were science nerds who had basic coding skills at best. I think I remember reading that Page had to buy a Java for dummies book to code up the back end for the search page prototype. And it was pretty amateurish even by the standards then. Scott Hassan was actually the one who did most of the early important coding work. Serge and Larry’s Pagerank PhD thesis algorithm was really what sealed their status as founders. We’ve sort of pinned the early days on those two but it was really a collaborative effort from a number of talented engineers to get it off the ground. But yeah with Facebook, as far as I know Zuckerberg was the engineering force multiplier for a very long time until it too grew out into its own superstructure.

Grandlord:
There are two types of programmers.

1) The ones who learn frameworks just enough to whip up an application. These ones are standing on the shoulders of the actual engineers because they rely on libraries, APIs and frameworks built by the engineers.


2) The actual software engineers who have a deep grasp of the concepts of algorithms, data structures, system design, architecture, design patterns etc. These ones are the programmer's programmer

Any self-taught programmer ambitious and curious enough, can always go from being the former to attaining the level of the later.

A CS graduate is expected to be an engineer already. He can easily learn frameworks if needed.

Just have a roadmap that shows where you're going and follow through with it. You can be the first guy and start earning some bucks but never ever stop there. Go deeper. Tech is fast changing and what's trending today might be outdated tomorrow. But the core fundamentals never change.

Where did this write up come from, thumbs up man. Where u dey now no.1 or no.2

africonn:


Where did this write up come from, thumbs up man. Where u dey now no.1 or no.2

From perusing information and research online

I'm self-taught, so I started out as number 1. Learnt the languages, moved on to frameworks and was able to put together functional apps with the logic, OOPs,and libraries. Frameworks and Platforms weren't really difficult to learn though. I just started building projects and I was good to go. Sharp sharp

It wasn't long until I realized I was floating. That was when I once had a problem making network calls for some API integrations. It led me into the deep world of networking, systems design, architecture, security etc. Still, another roadblock led me down the path of database management systems. Still another one led me into the world of unit testing and proper debugging.
Na my curiosity carry me enter these places sha

I still dey learn. But at least I know why these concepts are important and the roles that they play in the grand scheme of things.

Oh... I also stepped into the madness that is algorithms and data structures. These ones the MIT videos wen I watch make me reason whether na the same programming wey I know Na dia I know say levels dey inside this mata, forget am

So many things to learn, but for now I focus on learning DSA and systems design when I have the time. Man must make money with the little knowledge for a start. Na where the motivation dey come from

Grandlord:


From perusing information and research online

I'm self-taught, so I started out as number 1. Learnt the languages, moved on to frameworks and was able to put together functional apps with the logic, OOPs,and libraries. Frameworks and Platforms weren't really difficult to learn though. I just started building projects and I was good to go. Sharp sharp

It wasn't long until I realized I was floating. That was when I once had a problem making network calls for some API integrations. It led me into the deep world of networking, systems design, architecture, security etc. Still, another roadblock led me down the path of database management systems. Still another one led me into the world of unit testing and proper debugging.
Na my curiosity carry me enter these places sha

I still dey learn. But at least I know why these concepts are important and the roles that they play in the grand scheme of things.

Oh... I also stepped into the madness that is algorithms and data structures. These ones the MIT videos wen I watch make me reason whether na the same programming wey I know Na dia I know say levels dey inside this mata, forget am

So many things to learn, but for now I focus on learning DSA and systems design when I have the time. Man must make money with the little knowledge for a start. Na where the motivation dey come from

It's really deep, I admire your tenacity.

valzey:
There's this trend I've noticed with new developers where

They learn to code, build a few sites and suddenly want to be an entrepreneur. I see that as crazy. You don't have any experience about design systems and architecture and haven't worked on a real job to at least gain a tiny bit of experience so you don't make obvious mistakes.

They build a few sites, I'll admit that some are beautiful and post the links here for us to admire and encourage them. That's ok but what's more important at that level is code reviews, your site may be fine but your code would be poorly written with bad support for maintenance.

They learn about backend, follow a few tutorials though some may do it on their own but suddenly they want to make Facebook. All I can say here is LOL.

They learn to code but do not care about unit testing. The solution is obvious.

They discover optimisation techniques and overuse them. Just as there's premature ejaculation, there's also premature optimisation.

They do a few projects on their laptops and not care about source control. You must learn to use git PERIOD.

They think that getting jobs is easy, no my friends it isn't, sometimes you have to work with a messed up startup that's just as bad as a slave owner just to add years of experience in your resume.

They do not develop their problem solving skills, it's not easy but you can check out hackerrank and try their beginner problems to get acquainted.

They learn their stack superficially, I understand that it's not easy to go deeply in any stack but it's important. There's this interview I had regarding react, they asked questions in a non react way but expect you to respond in a react way. Some answers included Context API, Refs and design patterns.

They just stop at writing code. You should always try to be better than yesterday. Check out the SOLID principles and try to apply them to your projects, it'll make life easier for you especially during interviews and code maintenance.

The summary is know your level, develop a plan to improve and implement the plan. Never ever think you have arrived.

My advice is that try not to do these things.

Senior Devs in the community can contribute and I can update the list.

Op, please teach me programming, I am a complete novice in programming as I don't know Jack, but I'm willing and very interested in learning.

I am familiar with basic Computer Applications like MS Office etc... I even have a hp15 at home. Op please, I'm very obedient and humble, hardworking and diligent.

Or if you are very busy, you can refer me to someone else. Thanks.

pman06:


As a first class graduate of computer science, I believe I know more than you think I know, but then again I'll leave it at that.

Have a great day.

You don't know him that is why you open your mouth waaaah to say yen yen yen yen yen.
I'd leave it at that.

Pride [especially for the ignorant,] comes before a fall.

slyfran6:


You don't know him that is why you open your mouth waaaah to say yen yen yen yen yen.
I'd leave it at that.

Pride [especially for the ignorant,] comes before a fall.

Thank you.