If you're going to spend some time building these ideas, why not spend it on building something meaningful? These apps will be just glowing in your portfolio, but are totally useless. Why not solve somebody's actual problem with your skills? You might also suddenly grow a business this way.
Why do you think every developer makes the canonical todo app? From your perspective, that would be "useless". Is every developer teaching how to make a notetaker or todo app in the wrong?
To start building apps, we make what's familiar. What we use and know. And that doesn't therefore make those apps useless because we've seen them before or it wasn't an original idea. Only a very special few can start solving peoples' problems with code right off the bat. People just starting out building apps don't have a concept yet of how to structure it. That's what I've tried to do here--to get React developers to start thinking in terms of what they can build and inspire them to work on something meaningful.
I've built all of the apps that you see in the gifs above. Having these apps on my portfolio has helped me get work as an app developer and consultant. This is a proven approach to getting hired and moving ahead in your career. I bet many ambitious developers looking to get ahead would find that the polar opposite of "useless."
And finally, I want to make clear that I've echoed the need to build apps you find value in throughout the article, for example: "ask what features an app could have to make your daily schedule easier and go from there."
I mean they're useless in terms of utility - probably no one will ever use it, it will just rot in your GitHub repository. Maybe I wasn't clear enough - I don't mean they're totally useless, of course they give value in terms of getting a job. I could overlook that this is a "Learn React in 2020" series for newcomers, sorry 😅
Still waiting for your answer about todo apps, by the way.
Because it's an easy example to grasp the technology you want to use.
Jakub, I directly talk about making them based off of utility. Please read the post!
I've read the post. It doesn't matter that you talk about it. You won't use apps which you've created for your portfolio as it doesn't make any sense (there are plenty of free services out there that already solve your problem). So IMO their only purpose is to learn something, or have something to show off. They will still rot in the repository.
Only a very special few can start solving peoples' problems with code right off the bat.
I disagree. It's your choice. There's no "magic" here. Just find a problem which no one solved already, or build something better than someone else.
My point is: learn to build products, not portfolios and apps to show off. Building 1 simple product and giving it to users is a much bigger achievement than building 100 example apps for your portfolio. That's my opinion 😃
I'm interested in helping people become professional React developers, get hired, and level-up in their career, not turn them into entrepreneurs.
Any app you build will be more than useful to you and your career, not counting the new techniques and tools you get a chance to try out and practice. I can't count how many apps I built where the only utility was the chance to apply a new technology that just came out.
And no, they don't 'rot'. In multiple cases old applications that according to you were 'rotting' in my Github have been the basis for useful products that are the backbone of my business today.
Stop repeating falsehoods based on your 'opinion.' This is based on fact--build apps, build your portfolio and you will get ahead in your career.
This is not good advice. People need guidance before they build "products", whatever you mean by that. You admit it yourself: People build todo apps because "[they] are an easy example to grasp the technology you want to use."
Yes--they need to grasp the technology by building apps before they build products. This is what this post is about. There's no need to reiterate your opinion again.
I can't count how many apps I built where the only utility was the chance to apply a new technology that just came out.
That's exactly what I've said 😃
Stop repeating falsehoods based on your 'opinion.' This is based on fact--build apps, build your portfolio and you will get ahead in your career.
It's just my opinion, you can disagree with it, just like I can disagree with yours 😃
Yes--they need to grasp the technology by building apps before they build products. This is what this post is about.
No, they can build products and learn by doing it. No need to create apps just for portfolio. Your portfolio should consist of built products, not example projects for learning purposes. They might work for some of the employers, but clients don't care.
But again, this is just my opinion 😃
There's no need to reiterate your opinion again.
I'm just trying to explain as I clearly see that you don't get my point 😃
Some comments have been hidden by the post's author - find out more
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you're going to spend some time building these ideas, why not spend it on building something meaningful? These apps will be just glowing in your portfolio, but are totally useless. Why not solve somebody's actual problem with your skills? You might also suddenly grow a business this way.
Why do you think every developer makes the canonical todo app? From your perspective, that would be "useless". Is every developer teaching how to make a notetaker or todo app in the wrong?
To start building apps, we make what's familiar. What we use and know. And that doesn't therefore make those apps useless because we've seen them before or it wasn't an original idea. Only a very special few can start solving peoples' problems with code right off the bat. People just starting out building apps don't have a concept yet of how to structure it. That's what I've tried to do here--to get React developers to start thinking in terms of what they can build and inspire them to work on something meaningful.
I've built all of the apps that you see in the gifs above. Having these apps on my portfolio has helped me get work as an app developer and consultant. This is a proven approach to getting hired and moving ahead in your career. I bet many ambitious developers looking to get ahead would find that the polar opposite of "useless."
And finally, I want to make clear that I've echoed the need to build apps you find value in throughout the article, for example: "ask what features an app could have to make your daily schedule easier and go from there."
I mean they're useless in terms of utility - probably no one will ever use it, it will just rot in your GitHub repository. Maybe I wasn't clear enough - I don't mean they're totally useless, of course they give value in terms of getting a job. I could overlook that this is a "Learn React in 2020" series for newcomers, sorry 😅
Jakub, I directly talk about making them based off of utility. Please read the post!
Still waiting for your answer about todo apps, by the way.
Because it's an easy example to grasp the technology you want to use.
I've read the post. It doesn't matter that you talk about it. You won't use apps which you've created for your portfolio as it doesn't make any sense (there are plenty of free services out there that already solve your problem). So IMO their only purpose is to learn something, or have something to show off. They will still rot in the repository.
I disagree. It's your choice. There's no "magic" here. Just find a problem which no one solved already, or build something better than someone else.
My point is: learn to build products, not portfolios and apps to show off. Building 1 simple product and giving it to users is a much bigger achievement than building 100 example apps for your portfolio. That's my opinion 😃
I'm interested in helping people become professional React developers, get hired, and level-up in their career, not turn them into entrepreneurs.
Any app you build will be more than useful to you and your career, not counting the new techniques and tools you get a chance to try out and practice. I can't count how many apps I built where the only utility was the chance to apply a new technology that just came out.
And no, they don't 'rot'. In multiple cases old applications that according to you were 'rotting' in my Github have been the basis for useful products that are the backbone of my business today.
Stop repeating falsehoods based on your 'opinion.' This is based on fact--build apps, build your portfolio and you will get ahead in your career.
This is not good advice. People need guidance before they build "products", whatever you mean by that. You admit it yourself: People build todo apps because "[they] are an easy example to grasp the technology you want to use."
Yes--they need to grasp the technology by building apps before they build products. This is what this post is about. There's no need to reiterate your opinion again.
That's exactly what I've said 😃
It's just my opinion, you can disagree with it, just like I can disagree with yours 😃
No, they can build products and learn by doing it. No need to create apps just for portfolio. Your portfolio should consist of built products, not example projects for learning purposes. They might work for some of the employers, but clients don't care.
But again, this is just my opinion 😃
I'm just trying to explain as I clearly see that you don't get my point 😃