4 ms·
All the EEs I know think 1000 lines of code is "a lot". I've never met any EEs that used source control. I've never met any that tracked issues beyond forwardin
by moron4hire 11y ago
All the EEs I know think 1000 lines of code is "a lot". I've never met any EEs that used source control. I've never met any that tracked issues beyond forwarding emails back and forth. Their idea of documentation is separate PDFs for electrical properties and programming APIs.
So if us software engineers don't know the hardware side well enough to design hardware, I'm not really sure electrical engineers understand the software side well enough to design hardware, either.
Not saying there aren't EEs that understand software. Just saying I've never met any.
EDIT: wait, I know one EE who uses source control. I finally got my wife to start using Git. She kept looking over my shoulder at home, asking me "what is that?" pointing at my changelog in SourceTree. "Oh, you know, it's just an annotated record of every change every member of the project has ever made, including when they did it, in such a way that we can share these changes with each other without having to have long discussions about which particular folder on which particular network drive is the 'latest' code. Oh, you think that would be helpful in your work? Who would have thought?"
- sklogic 11y agoEvery EE company I worked for used source control (perforce, git or svn). And a typical Verilog module is far longer than 1000 lines.
- moron4hire 11y agoIf it weren't a meme, it wouldn't be a meme.
- cyanoacry 11y agoTwo things: 1) Of course, anecdotes don't prove the general case. 2) There's some conflation here between knowledge of toolchains and knowledge of software. Arguably, they are not the same--they might be orthogonal domains of knowledge. Knuth (who knows a lot about CS) does not use email, and I would be surprised if he used git for his books.