That's the reason why I still try to inspect the generated code to see how my problem was solved and if it reads plausible. There are also moments that I am surprised by the implemented solutions which look very elegant and "smarter" than what I could have come up. These are also the moments I learn from AI. I can even ask AI why it did things certain ways and it gives a nice summary of arguments. But I am often also critical towards AI if I am in doubt, resulting sometimes in a sort of discussion and sometimes I can convince AI (with more context) that the solution it created should take another route. It really feels like working with a really fast co-worker. And on top of that, I am better in writing up my thoughts to discuss things instead of talking with someone. Doesn't mean I don't discuss in real life with co-workers, but it is so easy to use AI for it too.

Then AI came a few years ago and that was interesting as a tool to play around with and do some simple small code (snippets) generation or as a buddy to discuss problems and find solutions. Meanwhile I was getting more and more bored with implementing stuff that I did already so many times at previous jobs. Same principles, different code base.

Last year I started at a new job and was at first hesitant, but I decided to go 100% AI with doing a rewrite of an existing application that will be phased out. So actually I could develop from scratch with the help of AI. First I copy/pasted code, then this year I found out about AI agents.

Never in my life have I been so productive in creating features/functionality while the code that AI generates doesn't differ that much from what I would have written myself. But then in a few prompts and 10 times as fast. Including unit tests. Which at many places that I worked were more often not a thing, then that they were.

Looking back at my 'career' it also made me realize that I do like "tech", but don't like coding as much as other software developers, I guess. I really like AI to make functionality and things working in a very short timespan. I enjoy 'AI-coding' much more than I'd have thought. So many things that you could/would not even try because it would cost too much effort, time or money. Now I can test within a morning a few different features to see which one fits best and works best.

I am now a happy 'developer' like I was when I started in this career a long time ago. I don't miss the coding part, at all. And AI will only improve, so personally I don't see a bright future for a lot of software developers to be coding in the traditional sense.

Then AI arrived a few years ago and two years ago I was still in hybrid mode, so partially using AI to lookup some code or generate some stuff and doing old school coding by hand. Last year I got a new job and from day one I am doing all software development in AI. I never want to go back to the old way of developing everything by hand. So many ideas I had in the past would cost too much time and money to even try. Now I can try five different solutions for a feature in a single day and select the one that fits best.

I was influenced and learned also a lot from older developers who were in their 50s to be sort of proud on coding, but that is fading away very hard. I also don't see code as something personal anymore or something I should be proud of. But I am proud of what I can create with AI nowadays, functionally. And I also found out that I like the creativity of making things more than the often boring coding.

When I see the AI generated code I think it looks really really well written. Of course it helps to steer it with certain design patterns or solutions you prefer, that's the one skill that is actually very valueable to be able to prompt well.

In the end the most important thing for the business owner is that things are working, they mostly don't every care about your code.

The main ingredients which imho make Doom classic:

- creepy/spacey/metal Adlib music, thanks to Bobby Prince (Adlib was good for that)

- simple, but effective spooky samples playing at random locations

- for the time good textures (need some good graphics artists) to give it a dark feeling

- kiss play experience (see how it probably would be done nowadays: http://www.youtube.com/watch?v=C4yIxUOWrtw )

- VGA-graphics, I keep saying this to people: VGA is pixely, but somehow I don't see that when playing Doom, I compare it with cartoon drawings, you don't focus on the details, but how it looks globally and use a bit of fantasy to bring it to life - nowadays graphics are so detailed that I somehow get distracted by too much detail, it's becoming too realistic almost and doesn't look like a 'game' anymore

- deathmatch or coop via modem, calling your friend to play a match via the telephone line, warning your parents that they are not allowed to pick up the phone, playing not too long because you had to pay per minute (in The Netherlands at least)

- everything packed in a few diskettes (3 or 4?) was at that time almost magic that you could have such a 3d world fitting on it

There are many more reasons why for me Doom will always have a good reputation for me, mostly because of a combination of properties which came together at that time.

People suggested Symbaloo, but that's only a nice iconic representation of hyperlinks. I don't think there is a site with the same concept as iGoogle. If anyone knows a good altenative then I'd really like to know to make my dad happy again ;)

I somehow understand the move of Google to stop doing iGoogle, because similar widgets are now by default integrated in Windows/Android itself.

Just one simple (real life) example:

  public String convertText(String text) {
   return text.toUpperCase();
  }

The point is in the end to keep the documentation in sync with the code and that takes indeed some effort. I myself always make documentation for a method in Java-doc style, so only above the method, if it's more complex than a simple getter/setter-method. I always tend to think in terms of the official Sun Java API-documentation, which I use(d) so often to know how all the classes/methods work, that it might also make my own code more readable/understandable when I or someone else has to work on my code if I have documented it. Inside the method code I try to comment little to not.

@snowwolf: I agree, but it's just an example to show that a method name should speak for itself

Not sure about the Google Alert if it is useful at all this way. I can manually search every day of course, but these are things I thought could be perfectly automated and done by Google Alert.