ProgrammerHumor
yourOutieWritesUnitTests
Discussion
That's basically how I learned programming.
Isnt that what any new language looks like?
After you've learned about a dozen languages, new ones seem only different in the IDE and the operating environment of the language. The syntax and features (like memory safety) are just things you look up quick and oh, yeah, got it, on with the coding.
(Not exaggerating at all. My early career included these systems: Xerox, CDC, Norden, Megatek, Aydin, Data General, IBM, Univac/Sperry/Unisys, Testdata/Interdata/Perkin Elmer/Concurrent, NordskData, SGI, Sun, and others. Learning Languages and environments was about half the job)
I mistook java (which I didn't know) for javascript, bluffed my way through an interview, and then had to learn java in the two months before I started the new job. Early career me was a mess :P
Early me got my first job as a programmer by claiming I knew Fortran. I knew assembly and Basic. Fortunately for me, the Fortran I had to work with at first was actually a simpler language than the versions of Basic I knew, so "fake it til you make it" was easy. (
UNIVAC Fieldata Fortran IV, for the record - it was obsolete even in the 70s. The only real challenge was adpating my 16-bit brain to a thirty-six bit word size.
- How do you fixed that bug?
- I have no idea, and I hope that I don't have to do that again any soon...
True story.
My very first exposure to coding somewhat is deciphering vb script in a dated excel file. Turns out it's converting the sheets into JSON files, so I learned what JSON is.
Hahaha laughs in *a whole project I have to run in a, not only a bunch of language, but also a framework, IDE and business jargon and logic I have no knowledge of*