Related Posts
The Bowl is oddly silent
Additional Posts in Software Engineering
Hi all, I’m transitioning from customer service to Devops. I’m looking for referrals in the following companies Amazon Google Microsoft Netflix Apple Cisco VMware Bank of America Citi Dell Facebook (Meta) IBM Lyft Mastercard Oracle Paypal I’m happy to discuss about my projects and qualifications. Thank you ☺️
I have a baby coming next summer. When should I tell my managers? I’m not particularly close to them JPMorgan Chase
With the economy being rocky, I’m afraid of getting fired. I would prefer to tell them at the later than sooner, like 3 months before delivery of the baby. Is that okay?
Should I submit on sedgewix first?
New to Fishbowl?
unlock all discussions on Fishbowl.
Any and all reference material is good, but the art of referencing is knowing where to find what you need quickly. It's also hood for sharing concepts with your peers. As an example, my wife was managing an engineering team and she rang me to ask about a problem one of her engineers was facing. I asked if he had a particular book, she said "yes, on his desk" I then said tell him to turn to page 72, third paragraph down, should start with Azure data... I'm fortunate to be able to visualise where information is in books once I've read them. Not so much with blogs, kindle books, stackoverflows or YouTubes though. The information architecture and structure is way different.
Knowing your reference material, where the info is, is a good way to help and communicate with others, much in the same way that design patterns are used. If you were to say to me "I need to do this, in that function" I could respond with that sounds like a Memento, Google it and see if it fits your actual circumstance.
The main point I'm trying to make is do use reference material and organise and catalogue it the way it fits you. The physical act of reading a book helps to set it in my memory and it works for me. Experiment to find the best way for you. Hope that helps in some little way
I do a mix. Usually on screen when I'm familiarised with the topic and/or skimming through.
On paper it helps me have full focus with no distractions. This helps because you have no choice but to focus on one thing. At the end of each section, I usually actively recall what I've read and write that down on notes. I use the Zettelkasten method for notes and it's been great so far for long term retention.
Both , but in terms of ratio mostly on screen to start to get the high level picture then re read in print to annotate and personalize.
The main books I read for SE and Algorithms are paper reference books I have had for years and years, and know where to find each relevant topic in them.
For ad hoc stuff, that’s more easily done online for me.
Paper because you can highlight/pencil pages AND it works like an extra screen if you're coding along and side-researching.
Unlike paper because I can flip backend forth between code listings and descriptions.
Paper. I don't know why but its really the only way my brain can comprehend it.