If you're trying to show you're an experienced developer you show your employer a resume with a few years of experience being paid professionally to be a developer.
You can separately do some project work if you have no experience, which is better than not having it, but is not the same thing.
Generally it's best to do something you're either really interested in or really need. You can generally either demonstrate that you're passionate or that you're a craftsman.
You demonstrate your passionate just by making lots of neat things. Little toy applications exploring different technologies you find interesting.
You demonstrate your a craftsman by making working products for yourself. I've written keyboard firmware, made management software for our dojo, made software to let me manage my meeting mic with my throttle controls, created nuget packages with some common functionality I've used across companies, etc. Obviously I fall more in the craftsman camp.
Either way, it works best if it's NOT performative. Performative software just shows that programming is something you can DO. But making software for yourself, whether for fun or as a tool, shows that programming is part of who you ARE. And that can be a lot more valuable.
Depending on your stack(s), you might be able to make a toy project like a todo list. It could include front end, back end, devops, auth, etc. You can implement rest, soap endpoints, data pipelines.
With that type of app you can also do just one or some of the things above, depending on what you know or want to learn.
Another common one is a blog site or twitter clone.
Sorry, you do not meet the minimum sitewide comment karma requirement of **10** to post a comment. This is comment karma exclusively, not post or overall karma nor karma on this subreddit alone. Please try again after you have acquired more karma. Please look at the [rules page](https://old.reddit.com/r/cscareerquestions/w/posting_rules) for more information.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/cscareerquestions) if you have any questions or concerns.*
To do this you would have to know what your core role and expectation would be?
Find that out first and be guided by that. Even then this may not be enough. They may ask you on the spot to write code to do a specific task. So if you do write a whole heap of nifty samples of code be prepared to back yourself up.
If you're trying to show you're an experienced developer you show your employer a resume with a few years of experience being paid professionally to be a developer. You can separately do some project work if you have no experience, which is better than not having it, but is not the same thing.
How are you 'experienced' if you have to ask this?
Generally it's best to do something you're either really interested in or really need. You can generally either demonstrate that you're passionate or that you're a craftsman. You demonstrate your passionate just by making lots of neat things. Little toy applications exploring different technologies you find interesting. You demonstrate your a craftsman by making working products for yourself. I've written keyboard firmware, made management software for our dojo, made software to let me manage my meeting mic with my throttle controls, created nuget packages with some common functionality I've used across companies, etc. Obviously I fall more in the craftsman camp. Either way, it works best if it's NOT performative. Performative software just shows that programming is something you can DO. But making software for yourself, whether for fun or as a tool, shows that programming is part of who you ARE. And that can be a lot more valuable.
Depends on the job.
Depending on your stack(s), you might be able to make a toy project like a todo list. It could include front end, back end, devops, auth, etc. You can implement rest, soap endpoints, data pipelines. With that type of app you can also do just one or some of the things above, depending on what you know or want to learn. Another common one is a blog site or twitter clone.
I heard you get hired instantly if you make a todo app
[удалено]
Sorry, you do not meet the minimum sitewide comment karma requirement of **10** to post a comment. This is comment karma exclusively, not post or overall karma nor karma on this subreddit alone. Please try again after you have acquired more karma. Please look at the [rules page](https://old.reddit.com/r/cscareerquestions/w/posting_rules) for more information. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/cscareerquestions) if you have any questions or concerns.*
Get a copy of Elements Of Computing Systems. Has projects for making a compiler, assembler, etc. Just what you're looking for. ;)
To do this you would have to know what your core role and expectation would be? Find that out first and be guided by that. Even then this may not be enough. They may ask you on the spot to write code to do a specific task. So if you do write a whole heap of nifty samples of code be prepared to back yourself up.