Who is updating CodeProject? (public video or write-up)
-
It would be great to have a public introduction to the people breathing new life into CodeProject. This could be a YouTube video or a written feature, ideally placed somewhere visible on the site.
A simple Zoom conversation with the author(s) would work well, but an even better option might be an interview hosted by a well-known developer YouTuber. A possible title could be: “CodeProject Reloaded: Conversations With the Next Generation.”
Some possible questions:
Personal Background
- Can you tell us a little about yourself—where you’re from and your background?
- Have you contributed to CodeProject in the past, for example through articles or community involvement?
Rebuild Story and Ownership
- What’s the story behind the rebuild of CodeProject?
- Who is behind the relaunch—was the site purchased, or is it under new ownership?
- Is CodeProject operating as a for-profit or non-profit project?
Team and Technology
- How many people are currently working on the site?
- What technologies is the site built on today?
- Was AI used in the rebuild, and if so, how?
Challenges and Future
- What have been the biggest challenges in bringing CodeProject back?
- What role do you see for the CodeProject community going forward?
- How can developers contribute or get involved today?
- What future changes or directions do you envision for CodeProject?
- Finally, what excites you most about this new chapter?
source(s): some questions and suggested title were suggested by ChatGPT
-
I know the tech stack is React/javascript (and probably typescript). I don't know what version of react, or if they're using a commercial react component library, making do with open-source packages, or crafting their own components (it would be difficult for outsiders to discern those details since react apps are minified when they're deployed).
I imagine they'll eventually put up a page that talks about it, but they obviously have bigger fish to fry right now.
-
I know the tech stack is React/javascript (and probably typescript). I don't know what version of react, or if they're using a commercial react component library, making do with open-source packages, or crafting their own components (it would be difficult for outsiders to discern those details since react apps are minified when they're deployed).
I imagine they'll eventually put up a page that talks about it, but they obviously have bigger fish to fry right now.
@realJSOP said in Who is updating CodeProject? (public video or write-up):
I imagine they'll eventually put up a page that talks about it, but they obviously have bigger fish to fry right now.
"bigger fish to fry" and more important things for sure! They seem to be moving through them pretty quickly though.
With LLMs I think CodeProject will change. Anyone can just create a great article in minutes these days and post it. I think that is okay (if they note the LLM used to create it) but there will need to be some kind of filter as we might get zillions of articles... and maybe that is okay also. It's just going to be different now. Sorry, I am just rambling. =)
Thanks for the feedback.
-
@realJSOP said in Who is updating CodeProject? (public video or write-up):
I imagine they'll eventually put up a page that talks about it, but they obviously have bigger fish to fry right now.
"bigger fish to fry" and more important things for sure! They seem to be moving through them pretty quickly though.
With LLMs I think CodeProject will change. Anyone can just create a great article in minutes these days and post it. I think that is okay (if they note the LLM used to create it) but there will need to be some kind of filter as we might get zillions of articles... and maybe that is okay also. It's just going to be different now. Sorry, I am just rambling. =)
Thanks for the feedback.
@Ryan-Scott-White said in Who is updating CodeProject? (public video or write-up):
@realJSOP said in Who is updating CodeProject? (public video or write-up):
I imagine they'll eventually put up a page that talks about it, but they obviously have bigger fish to fry right now.
"bigger fish to fry" and more important things for sure! They seem to be moving through them pretty quickly though.
With LLMs I think CodeProject will change. Anyone can just create a great article in minutes these days and post it. I think that is okay (if they note the LLM used to create it) but there will need to be some kind of filter as we might get zillions of articles... and maybe that is okay also. It's just going to be different now. Sorry, I am just rambling. =)
Thanks for the feedback.
I hadn't even thought of the AI article thing. Maybe they should ban them right now, before it becomes a problem.
In my case, there's no way I could get an AI to write an article using my patented blend of wit, cynicism, sarcasm and outright condescension. You guys would be able to tell. :)
I think I'll try it with this prompt:
"Write an article about developing a WPF wizard in C# and DotNet Framework 4.8 in the writing style of John Simmons/Outlaw Programmer."
-
OMG! This is the lead-in that ChatGPT gave me!
<br/>
Building a WPF Wizard in C# and .NET Framework 4.8 – The Outlaw Way
Let’s face it: nobody likes wizards. They’re slow, they break the flow, and they usually exist because the designer couldn’t come up with a decent UI. But sometimes, the world hands you a requirement wrapped in a Gantt chart, and the words are carved in stone: “We need a wizard.”
Fine. Let’s build a wizard. But we’re going to do it our way: clean, reusable, and free of the spaghetti XAML vomit you’ll find in the average StackOverflow answer.
After that, there was some example code, and it ended with this:
"Final Words
Building wizards doesn’t have to be a soul-sucking ordeal. Define a contract, give the controller the brains, and keep the UI dumb. That’s how you stay sane in WPF land.
Because if you’re going to build a wizard, build one that doesn’t make you hate yourself six months later.Final Words
Building wizards doesn’t have to be a soul-sucking ordeal. Define a contract, give the controller the brains, and keep the UI dumb. That’s how you stay sane in WPF land.
Because if you’re going to build a wizard, build one that doesn’t make you hate yourself six months later."
