by austin-cheney on 11/17/2024, 3:31:51 PM
* Recursive file system management tools. Most developers cannot navigate a tree model and cower in great fear
* performance analysis/monitoring tools. Most developers are astoundingly bad at performance and then lie about it with weird unfounded guesses
* markdown to html parser or the opposite. Most developers have no idea the actual cost of involvement required for basic string parsing and wrongly believe it’s free
* network proxy. Aside from authentication this is mind blowingly simple. Most developers will supremely over engineer this
* API documentation. In a world where the average developer struggles to write an email actually describing inputs, purpose, and outputs clear enough for a stranger to follow can be quite the impossibility
by ostaquet on 11/17/2024, 7:01:52 AM
A video game. Any kind of video game.
It is fun to develop, rewarding and the dynamics inside the code are always interesting (input from the player, performance, graphics, etc).
Even a simple game that can take an afternoon or a day to develop bring some fresh air.
by mooreds on 11/16/2024, 9:01:19 PM
I think writing a book about something technical. Either self-published (I like leanpub) or through a publisher. Doesn't have to be long, even a 30 page ebook is a big effort.
I have done this a few times and you learn so much and appreciate so much.
Other than that, I think it really depends on where you are starting. If you are a webdev, building an MVC framework. If you are a system programmer, building a basic HTTP.1/1 web server.
by dgunay on 11/17/2024, 9:38:32 AM
Doing a programming language/compiler was very educational and did a lot to demystify computers for me.
I would also second the recommendations to write a game. If for no other reason than the fact that it is some of the most fun programming there is, you usually get to flex muscles you'd never get to in a boring web dev job.
by Lionga on 11/16/2024, 8:15:15 PM
A ProjectContractChargingPeriodProjectAccountReferenceVMFactoryBuilderStrategy Implementation
by mikewarot on 11/16/2024, 7:59:33 PM
Text editor, compiler, BASIC interpreter, virtual machine emulator, CRUD application, web server, Lisp interpreter, Forth Interpreter, SQL database application.
Repeat the above as gui applications, and on the web.
by meiraleal on 11/17/2024, 12:15:41 AM
An ERP and a blog engine with the first post being about it
by readyplayernull on 11/19/2024, 1:35:57 AM
Automation tools for your own use. I did my own job offer web scraper. I've saved lots of time and pain automating work.
by jryan49 on 11/16/2024, 7:43:05 PM
A video game engine
by yen223 on 11/17/2024, 12:05:52 AM
An overdesigned, overengineered personal website
by fluffyspork on 11/17/2024, 12:41:32 AM
JPEG codec
MPEG 1 codec
Minimal HTTP server of actually used features.
by bjourne on 11/16/2024, 9:24:57 PM
A raytracer and an emacs mode.
by chistev on 11/16/2024, 9:12:00 PM
An ecommerce website.
by Hashex129542 on 11/19/2024, 1:07:37 AM
Bots
by coldtrait on 11/17/2024, 6:14:06 PM
A Todo list /s
By this I mean what project should everyone build not because its useful or new, but because the process of building it forces you to learn something new. Some examples I've heard are your own programming language or a simple implementation of a database.