I keep an engineering notebook. In it are meeting notes, phone call notes, and some engineering drawings and scribbles.
I keep one or more three-ring binders for a given project. Number and size depend on size and duration of said project. Often-referred-to data sheets, drawings, plots from test equipment, lengthy derivations, photocpies of a critical page from a book, printouts of key journal papers...
I also keep a project folder on the PC with many directories. I try to divide a project up into logical sub-folders. There will be folders for data sheets, relevant papers (with sub-folders for topical organization), documents (reports, proposals, presentations, etc), overhead stuff (like pdfs of orders and receipts), cad files, and folders for individual cad tools (one for spice, one for microwave circuit simulator, one for 3D field simulator, one for firmware, etc, etc). One for photos - I take a lot of pictures of things with my phone to go into reports and presentations. Others for special purposes that make their need known when they show up.
The notebooks stay on my shelf, except for the current one, which goes with me everywhere. The binders generally stay in the office, except for the small one with currently-used stuff, which typically travels with me to meetings and home at night. The PC gets backed up onto a server AND a desktop hard drive.
Finally, my laptop is heavy since I don't have a desktop. I don't always like dragging it home. So I have files I may be currently working on (a proposal or a drawing or a simulation) also on a thumb drive, and schlep that back and forth so that I can get some work done off site without dragging the whole PC around.
Finding things again is key. On the PC I can search. In binders, I use dividers and label them for organization. Key things are at the front of the binder, and may get individual sticky notes/tabs. I have been known to use those also in my lab engineering notebook, and I summarize critical and frequently used information on the back page.
This whole mess has been evolving ever since I started designing anything, even before I went to college, and it just continues to change as the tools of our profession change.
@David: This was in 2011 so maybe we should ask him to update his experiences...Max??
It's strange that something as ubiquitous as emaisl shoudl cause so many problems. For my personal emails I'm still using the same scheme you mentioned. I have a Google Apps account that gathers all of my email messages from the various accounts that seem to poliferate over the years. I use Outlook and Google Sync on all my personal machines, which means that all of the machines always re-sync when I power them up (and keep resyncing whilst powered up) and any actions like email messages that I send, receive, delete, whatever on one machine are replicated on all of the others.
I also have my UBM/EETimes notepad with my email@example.com email account -- that has to be handled seperatly (sad face)
Fortunately I am not as famous as you or Max so I don't need to think about this sort ot thing, but Max seems to have found a good solution. This was in 2011 so maybe we should ask him to update his experiences...Max??
I like using thunderbird. This allows for multiple accounts and lots of sub folders. For mailing lists, I have search patterns which sort the list into it's own digest folder.
Thunderbird sets up a local fork, which is an accountless email client. Useful when working with IMAP hosts. It is also possible to set up additional headless POP accounts. Works good for archival mail.
Sent and received messages can be copied to these headless account folders, where little icon allows the correspondence to be see in a threaded view.
I keep a folder named sync, for temporary messages or when I am traveling and need to download emails.
@Spike_johan: Interestingly, this is what most trainee engineers suffer from in their first couple of years. "If you didn't write it down, you'll forget it" and "If you didn't write it down, you didn't do it". It is through hardship do they understand the importance of physical documentation. Going tech-savvy is good, but in order to build a technology, paper documentation is required.
I like to document my work with the help of a simple technique: locality of reference. This means that I keep at hand those things that have equal importance to a project, even if I don't use them. Not only that, I label each section using the alphabets A,B,C etc, and write a summary of contents on top of every label. If I need a document on Software Post Processing that has been labelled in "T" and if the topics Software String Management in "Z" and Software Code Debugging Models in "R" are equally important to the project (even if they are not needed), I group the labels T,Z and R together.
@DrQuine - The challenge of documentation is that it is usually intended for retrieval in the future.
What I have found using the smaller one inch binders is that this size works for keeping the quick reference stuff. The few pages of the data sheet one needs to access quickly like the pinouts and footprints. I also keep the schematic, and BOM in these thin binders. I like to think of these as aking to the "pocket program guide." for easy quick reference.
Size does matter here as I like to reference some of these as a bedside reader. The photograph was taken literately on my bed. This size is also useful in the bathroom. Granted one can take the laptop, or phone into the loo (head or necessary) Given that most of these now have Orwellian cameras on them, I am not sure I want to do that. Or for this natural engineering and salty sailor talk topic to continue.
@Karen - My folders are quarantine, sandbox and guff. Then there is the evenMoreGuff folder. Disks and now thumb drives that I sneaker net with are called Noah, and ark. These then go into quarantine.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.