The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I continually have to check the details of syntax and stuff when programming. Things like print format specifiers, the syntax of things I havent used for a year or so, and use a calculator to work out bit masks and check my bit wise logic. I can never get it right in my head.
I dont remember details. I dont pride myself on that. I spend my time and energy on the big picture. Designing and understanding complex mechanisms. The architecture. The guts of the machine.
So I think of myself as a software engineer, not a programmer.
Same with me. There's so much crap to keep track of nowadays I think it's better to understand principles and Google the detail specific stuff as needed. Because as sure as the sun rises in the east, there will be some new fancy buzzword come along every other day that we're expected to magically know just because it's the next shiny red button to come along.
I'm the Chief Bit-Byte-Blob Combobulator in my company (of one
Technically, a "Software Engineer" might not do any actual "Programming" - maybe just designing/architecting. So I don't think it's always an equivalency. $0.02
Last Visit: 31-Dec-99 18:00 Last Update: 20-Aug-18 0:49