Readit NewsI have a couple projects I could see this being really useful in, at least as an option instead of pure plain text. I still feel like consumers don't like markdown though, it's frustrating.
One thing I noticed, when doing a list (bullet, numbered etc) it would be great if the list continued on barrage return (enter) - most general users would expect that I think.
That said, VSCode is a popular platform for this for exactly the reason I think consolidation is eventually inevitable: it's got a huge preexisting ecosystem. There are extensions for practically anything you could ask for.
There's likely room for some standalone, focused apps in this space. I just don't see the current wave of "we put a wrapper around Claude Code and gave it some basic MCP and custom prompt management tools like a dozen other applications this week" being sustainable.
They're all going to end up on their own tiny islands unless there's a reason for an ecosystem to develop around them.
A tiny island is fine for a tool like this - not everything needs an 'ecosystem'.
Same as StackOverflow, same as Google, same as Wikipedia for students.
The problem is not using the tools, it's what you do with the result. There will always be lazy people who will just use this result and not think anymore about it. And then there will always be people who will use those results as a springboard to what to look for in the documentation of whatever tool / language they just discovered thanks to Cursor.
You want to hire from the second category of people.
I am from the generation whose only options on the table were RTFM and/or read the source code. Your blend of comment was also directed at the likes of Google and StackOverflow. Apparently SO is not a problem anymore, but chatbots are.
I welcome chatbots. They greatly simplify research tasks. We are no longer bound to stake/poorly written docs.
I think we have a lot of old timers ramping up on their version of "I walked 10 miles to school uphill both ways". Not a good look. We old timers need to do better.
1. green field project 2. other people's legacy project 3. your green field project growing into legacy project.
You can learn so much from each of these, but to me the most eye opening experience was our green field project growing into a project with more and more developers.
You could learn so much about others, some were very arrogant, went on constant refactoring mission only to mess up everything. If for some reason, I couldn't check what they did, usually, I had to come in and fix their stuff, but sometimes the only person knowing about the edge case was me, so I just left it "messed up".
Others tried to understand why the system ended up this way, some accepted it, while the best actually improved the system by looking back and recognizing the simplicity hiding in the mess.
This is always a fun one...
"Who wrote / designed this garbage... Oh wait, it was me"
God forbid you have to remember to save your work!
How much time I put to this really depends on what else is happening in my life at the moment. There has been months where I've put total of 5 hours into this and some weeks alone I may reach close to 40 hours.
I would imagine this will set you up incredibly well for a career in the industry, arguably moreso than your actual degree. Any reasonable prospective potential hirer is gonna be super impressed by it I think.
Nothing sinks in to anyones brain because they're not actually talking about it and they don't need to actually learn it for any reason in school because they can just ask the chatbot again at any moment.
I am trying to remember why their software became considered ubiquitous for caching and sessions, and I reckon many a framework is busy rectifying this choice, as we speak.