Skip to main content

A New Year...A New Month...A New Technology...

I have (first correction - thanks Matt!) been pulling together links for a larger "start of the year" post and decided to scale it back and try something a bit different. The various sites that AKSEL manages will be going through a "re-branding" exercise in the near future but one of my goals this year is to follow Chris Brogan's Three Words idea (Freedom. Consistency. Communication - I'm still deciding...) as well as working in some of Mark Riffey's ideas into my weekly schedule.

Rod Paddock asked "What's in a title" - and pointed out that one thing developers can do to become better developers is to adopt more agile practices - and he lists several practices and his experience with them.

That's a great goal for developers but what about "database developers"? There are lots of developers out there but almost every role needs to be qualified further: web developer, application developer, database developer. Are there other qualifications that are needed?

A regular Windows application developer likely doesn't need to know about CSS - but a web developer better know CSS. Does a database developer have to know the normal forms? Or maybe how to design a database properly?

How do you qualify that? Because there are always exceptions to each rule.

One of the ways I'm starting this year is by taking a new technology each month and really exposing myself to it (insert joke here). What's my guideline? I'm not completely sure but my first technology (MVC) is something that is actually fairly broad - popularized with Ruby on Rails, "foxified" with FoxTrails and DotNetted with ASP MVC.

How do *you* plan to become a better developer?

Comments

Eric Selje said…
I finally joined IEEE Computer Society (computer.org) for $99, which give me access to Safari Online and a TON of training videos. I'm looking forward to retraining myself with some new technologies.

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. ...

Respect

Respect is something humans give to each other through personal connection. It’s the bond that forms when we recognize something—or someone—as significant, relatable, or worthy of care. This connection doesn’t have to be limited to people. There was an  article  recently that described the differing attitudes towards AI tools such as ChatGPT and Google Gemini (formerly Bard). Some people treat them like a standard search while others form a sort of personal relationship — being courteous, saying “please” and “thank you”. Occasionally, people share extra details unrelated to their question, like, ‘I’m going to a wedding. What flower goes well with a tuxedo?’ Does an AI “care” how you respond to it? Of course not — it reflects the patterns it’s trained on. Yet our interaction shapes how these tools evolve, and that influence is something we should take seriously. Most of us have all expressed frustration when an AI “hallucinates”. Real or not, the larger issue is that we have hi...

Friend vs Therapist vs LLM: Shades of Grey

The conversations with AI series brings up a single point and then compares it between different LLM engines. These types of conversations were one of the many contributing factors to my writing of " Towards Consciousness " that explores the benefits and issues of creating a conscious AI. In this scenario, I was interested in seeing how an LLM might differ from a friend or therapist on issues that may have nuanced responses or contexts. In doing so, I came up with an interesting discussion on shades of grey. My Premise: Is it a bit strange to be using an LLM as a sober second thought? Every time I walk down this path of “why use an LLM to do certain things”, I come back to the alternatives that people like to say. “Why not bring it up with a friend?” A friend typically has your back or will say whatever to support their own agenda. “A therapist?” That’s someone who is “trained” to be impartial. But a computer? A computer is impartial based on two logical outcomes. If you say ...