Skip to main content

Breeding lazy developers...

Andy Kramek asked back on February 19th (I've been badly missing my reading and Alex pointed me to it - since he's first on my alphabetical listing of Fox bloggers)

Are on-line technical forums breeding lazy developers

The discussion (found in the comments) is a good one but what it also illustrates is a lack of resources or pointing to resources about how to get started in certain issues. As our development environments get larger and more features, it's hard to know where to start. In addition, the help files are often written to say "here's what this does", not "how to do it". I fully agree with Andy's issue about using CREATE CURSOR from ARRAY. That's just crazy. But for those who are posting "How do I create this...", these should be used as great fodder for the various How To sites and I think everyone should be linking to them.

For example, Craig Boyd's posts about learning Visual FoxPro

Craig Bailey's Screencasts on the same

The great VFP Seminar series from VisionPace

I'm sure there are some more - but while developers may seem lazy when they don't RTFM or google for examples, it's also the case that searching between 12,000 articles in Google can be hard to separate the wheat from the chaff. Asking the "forums" may be a way of trying to filter it down.

I'm not saying anyone should be writing the code for anyone - but pointing them to places where they can find basic introductions is a great way to redirect them. Maybe every forum should have pinned topics that say "Before you post a "how do I" topic, go here first"


powered by performancing firefox

Comments

Popular posts from this blog

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

I’m Supposed to Know

https://programmingzen.com/im-supposed-to-know/ Great post for developers who are struggling with unrealistic expectations of what they should know and what they shouldn't. Thirty-forty years ago, it was possible to know a lot about a certain environment - that environment was MS-DOS (for non Mac/UNIX systems). . There was pretty much only a handful of ways to get things going. Enter networking. That added a new wrinkle to how systems worked. Networks back then were finicky. One of my first jobs was working on a 3COM + LAN and it then migrated to LAN Manager. Enter Windows or the graphical user interface. The best depiction of the complexity Windows (OS/2, Windows NT, etc) introduced that I recall was by Charles Petzold (if memory serves) at a local user group meeting. He invited a bunch of people on the stage and then acted as the Windows "Colonel", a nice play on kernel. Each person had a role but to complete their job they always had to pass things back to h...