4 ms·
Did you use VB6? It was less a language and more of a wysiwyg windows desktop GUI application builder. If that's what you learned in school and it was your fi
by stcroixx 4y ago
Did you use VB6? It was less a language and more of a wysiwyg windows desktop GUI application builder. If that's what you learned in school and it was your first professional job, you would have a very difficult road ahead of you learning something like C. Maybe 3 out of the 20 were successful moving on. Some VB apps had almost no code at all that wasn't auto generated by the platform and bound to UI elements to handle button clicks and so on.
- Jtsummers 4y agoI did, yes. But not a lot. > Some VB apps had almost no code at all that wasn't auto generated by the platform and bound to UI elements to handle button clicks and so on. Then they weren't programmers, so I could see them having to "reskill" (actually become programmers). But if they transferred to another wysiwyg toolkit then there is still no reskilling, just relearning (as I mentioned in my cousin comment to this one). Knowledge isn't skill, it's just knowledge. If your knowledge ends at "I know how to use this particular toolkit" and your skill is "I can do it quickly, make it functional, and make it pretty" then the skill should be transferable while the specific knowledge may not be and you may have to learn new knowledge. But the skill remains.
- pjmlp 4y agoJust like using VB.NET with Windows Forms, and version 2 introduced back all the Me stuff and some of the semantics that were initially left out. I not only used VB 6, I used version 3 when VBX was the only option for 3rd party components.