I would like to piggy back on this post to mention that I'm willing to work for Latte, especially if you also have a shower or food. I'm based in Sydney, Australia and you can find me on LinkedIn.
The VB6 IDE was Ok for 1998, but 1998 was a long time ago.
I still use VB6/VBA to get shit done, but only because I have a bunch of code & tools I've already written in or for it. I can see how it would be pretty useless to most people.
Registry-free COM has solved all of the versioning issues for me.
Language-wise, I find it's limitations to be its strength - kind of like ouilipo for programming.
Not really. There were other hypertext systems at the time, but the early HTTP and HTML were clearly the minimum viable product that kicked off the progression towards what we have today.
I'm having this problem right now. Simulation/Entity type object model is working quite well for one app, but add another app and the cracks in the abstraction become obvious.
Using dynamic properties for the app-specific properties seems to help contain the problem. Also, putting app-specific code in extension methods.
I see this problem as a limitation of our current tools. Splitting the object model into separate perspectives is too hard right now.
I laugh when I see positions advertised with "senior" in the title that are only asking for 3 years experience. Around here, that's normal. Does this happen in other industries?
I can feel for him. I often find buzzwords are used to describe things I've been doing for 10 years in a way that makes it seem like people who only just discovered that thing are "more current" than me.
It's frustrating, and it actually comforts me that this can happen even to the likes of Larry Ellison.
