4 ms·
Show me a system you’ve worked on that wasn’t put together from knowledge from previous education and jobs (yours and others), documentation from vendors, stack
by mlhpdx 4y ago
Show me a system you’ve worked on that wasn’t put together from knowledge from previous education and jobs (yours and others), documentation from vendors, stack overflow, code generators , etc.
I would hate to be a stakeholder in a company whose value depends on employees not talking about and reusing the incremental skills and knowledge gained while working there.
- bqmjjx0kac 4y agoThis is a pretty common situation in the US for folks who work on government contracts.
- alistairSH 4y agoYup. I’m outside DC. Somewhere near half my software engineer (and adjacent fields) friends are under contract to either the military or NSA/CIA. Most of them with TS/poly clearances. Ask one of the what they’re working on and the most you’ll get is something like “dig data on platform X”. If platform X is something public, they could talk about the platform. But, talking about any project specifics, implementation details, etc would be a felony.
- fatneckbeard 4y ago[flagged]
- tourist2d 4y agoNDAs don't care where you sourced your knowledge from.
- deleted 4y ago[deleted]
- 8note 4y agoIm pretty sure I learned a full set of new skills at my current job. I don't think knowledge on any particular api is particularly useful compare to the more generic "can you read docs and use apis" skill, which is directly applicable from something like high level hard ware work making an ftdi USB chip go brrr to making dynamoDB work nicely, but I definitely didn't know anything about dynamodb before doing a server/web job Async distributed systems and FPGA vhdl have some overlap in how you build things, but doing an interview based on my old FPGA skills likely won't show much of my servers and databases systems design skills