faebudoMar 8
Su-Shee

at the end of the day I realize over and over

* knowing technology really well, knowing how "it" works is worth investing time
* you only need a handful tools and a few languages to build practically everything you want
* good documentation is worth it - reading it and writing it
* testing, validating, measuring - whatever you want to call it is worth knowing really well

Mar 7 at 1:57pmWeb
Show threadm3t00🌎🇺🇦Mar 7
@sushee
all valid points. In my experience, the main thing to understand is the big-picture system. component details, manuals etc. can be referenced as needed to fine tune and troubleshoot. learning how a battery is built is of little use to someone who just drives the car. Memorize the algorithms, document details so you don't have to remember everything. works for my limited brain space.
Show threadSimon WillcocksMar 7

@m3t00 @sushee I worked on a small part of the ground segment of a major weather satellite system nearly 30 years ago. The printed requirements filled literally a shelf of folders, detailing protocols, font usage, colours, etc.

We dove into them for weeks, trying to understand the system until one day someone came across a single powerpoint slide that showed that the satellite didn't just transmit raw image data to the ground, but was also a comms relay. Suddenly it all made sense!