reclifetextidea

Idea:

Name:
CoderFail.com

Description:
A website for inspiration, humor and info when you’re in a learning or development rut.
It would include content such as well known coders getting things wrong, for example one of their first or earliest for loop efforts going horribly wrong.
This would encourage new and developing learners to understand that even the greats in the field get things wrong when they’re learning, and probably still do.


General Website Plan:
Main top of the page would be the hero image type thing, with navigation links along the absolute top of the page, as hoverable drop down link menus to other content.

On the content of the main page, we could have:
A main featured image of the latest ‘CoderFail’, which would be the link to the latest persons story, their code fail, the common beginner mistakes or misunderstandings they were making, and how they could have improved directly at that point.

A blog about learning to code.  Self written, but could also host other learners.  Doesn’t have to be confined to new learners, can be others in tech careers who are learning a new language for their roles, allowing any user to almost self journal their development careers or journeys.

Other site features could include:

A community forum for general discussion of, sharing and troubleshooting  all things code,
A built in chat-room, showing usernames, scrolling text, all that kinda jazz.
Latest IT Meme humor.
Links to featured blog posts by members.
Links to articles about a range of topics including:  learning to learn, the process of developing a learning plan for your chosen technology or career goal, latest tech developments,other stuff I can’t think of right now and hosted articles by other/external authors.
A podcast speaking with current coderfail members about what they’re working on , things they’re finding tricky, take comments from listeners on how to fix, discuss etc.

Ways the website could generate revenue:
Initially,  self funded/by donations.
Courses about both tech and soft life skills/motivationals etc.
Affiliation links/articles.
Minimal but present very related ads.
Eventually, companies could pay for their ‘coder fails’ to be sponsored/hilighted, along with links to their companies web, products etc.
Job boards of some sort.

Stretch goals:
Finally, a mentorship/development buddy system, paid initial membership (very low costs or low subscription, to cover mentors time and resources), for someone to work with you while you learn to code.

Long term / Really Difficult Goals:

A CoderFails Application you can open which is actually a pair programming application, based on an almost ‘messenger’ application type chat.
It would still be a live chat, but you’re speaking only in your code blocks.  Here’s how it would work:
	Person A with the problem posts the codeblock to Person B, a mentor or member registered as knowledgable in the language Person A has trouble in.
	Person B reviews the code, and corrects/points out issues.
	The updated code would be posted each time, any corrected issues having a tick next to them.
	If all code errors are correct, all should have ticks.
	Person A and Person B tick to approve all changes, and close the message.

	When the user is finished, they can review the person who helped them by upticking.  This  	would be counted as part of a users overall user account on the website as a running total.

	So many ticks to your account unlocks more content, access to parts of site, free goodies etc.
Idea:

Name:
CoderFail.com

Description:
A website for inspiration, humor and info when you’re in a learning or development rut.
It would include content such as well known coders getting things wrong, for example one of their first or earliest for loop efforts going horribly wrong.
This would encourage new and developing learners to understand that even the greats in the field get things wrong when they’re learning, and probably still do.


General Website Plan:
Main top of the page would be the hero image type thing, with navigation links along the absolute top of the page, as hoverable drop down link menus to other content.

On the content of the main page, we could have:
A main featured image of the latest ‘CoderFail’, which would be the link to the latest persons story, their code fail, the common beginner mistakes or misunderstandings they were making, and how they could have improved directly at that point.

A blog about learning to code.  Self written, but could also host other learners.  Doesn’t have to be confined to new learners, can be others in tech careers who are learning a new language for their roles, allowing any user to almost self journal their development careers or journeys.

Other site features could include:

A community forum for general discussion of, sharing and troubleshooting  all things code,
A built in chat-room, showing usernames, scrolling text, all that kinda jazz.
Latest IT Meme humor.
Links to featured blog posts by members.
Links to articles about a range of topics including:  learning to learn, the process of developing a learning plan for your chosen technology or career goal, latest tech developments,other stuff I can’t think of right now and hosted articles by other/external authors.
A podcast speaking with current coderfail members about what they’re working on , things they’re finding tricky, take comments from listeners on how to fix, discuss etc.

Ways the website could generate revenue:
Initially,  self funded/by donations.
Courses about both tech and soft life skills/motivationals etc.
Affiliation links/articles.
Minimal but present very related ads.
Eventually, companies could pay for their ‘coder fails’ to be sponsored/hilighted, along with links to their companies web, products etc.
Job boards of some sort.

Stretch goals:
Finally, a mentorship/development buddy system, paid initial membership (very low costs or low subscription, to cover mentors time and resources), for someone to work with you while you learn to code.

Long term / Really Difficult Goals:

A CoderFails Application you can open which is actually a pair programming application, based on an almost ‘messenger’ application type chat.
It would still be a live chat, but you’re speaking only in your code blocks.  Here’s how it would work:
	Person A with the problem posts the codeblock to Person B, a mentor or member registered as knowledgable in the language Person A has trouble in.
	Person B reviews the code, and corrects/points out issues.
	The updated code would be posted each time, any corrected issues having a tick next to them.
	If all code errors are correct, all should have ticks.
	Person A and Person B tick to approve all changes, and close the message.

	When the user is finished, they can review the person who helped them by upticking.  This  	would be counted as part of a users overall user account on the website as a running total.

	So many ticks to your account unlocks more content, access to parts of site, free goodies etc.


Required Technologies/Stacks
HTML5, CSS, JS while early developing/semi-static (I’m leaning towards either flex or tailwind).
MERN Stack as I progress.
Database for user details, profiles, all that good stuff, MongoDB.
Express for routing type stuff.  I think, I don’t really know anything about express yet.
React for front end design componenty state type stuff.
Node.. for .. node.. yes..
(Basically, build the website, blog etc WHILE actually learning to code, ie, learning about and writing about learning the mern stack as I use it to develop the community.




Required Technologies/Stacks
HTML5, CSS, JS while early developing/semi-static (I’m leaning towards either flex or tailwind).
MERN Stack as I progress.
Database for user details, profiles, all that good stuff, MongoDB.
Express for routing type stuff.  I think, I don’t really know anything about express yet.
React for front end design componenty state type stuff.
Node.. for .. node.. yes..
(Basically, build the website, blog etc WHILE actually learning to code, ie, learning about and writing about learning the mern stack as I use it to develop the community.
---------------------------------------------------------------------
more to add below.