Code & Coffee recap 8/27/2021

 Topic: Back to School.   Summer is over, it's time to hit the books,  what are you going to brush up on in the next few months?

QOTD: “I applied bootstrap, what more do you want”

• Graphic design history
• Graphic design vs front end dev
• Language learning
• DUO lingo has sad owls
• Why the hate for PHP
• forced input sanitization?

Intermission while I helped to get the kid’s car started

• A case study in interpersonal interactions and work relationships between “Product” and “Engineering” teams
• A brief discussion on age in software development
• Is there a push out or do the grey hairs get lost in the sea of newbs?

And we will save the topic for another time, since is it mostly unused.

Code & Coffee recap 8/20/2021

Topic: Favorite historical computer… deferred to future since we didn't really get onto the topic today.

• Talked about Helium mining and antennas a little bit
• Just need to get a few more meters up and can 
• Streaming data and web api
• Makes better use of threads
• High potential for better resource utilization
• Check out R2DBC and WebFLUX for more ideas
• Summer is almost done
• And some are ready for it to be done
• Mental context build time
• Takes 20-30 minutes post interruption to rebuild context
• Talked about what BNB in “AirBNB” really means
• Useful for making docs sites: https://gohugo.io/

 

Code & Coffee recap from 8/13/2021

 Topic: Conway’s Game of Life Challenge part 2 what did you learn.

• High school was so long ago (for some of us)
• Conway’s game is one of the exercises at Code Retreat
• Global Day of Code Retreat is coming up in November
• Looking into the possibility of hosting in Grand Rapids
• https://www.coderetreat.org/
• What did we learn
• It takes a little while, especially the first time or the first time after a while
• Talked about some of the trade offs that can be surfaced
• Memory usage for a big grid
• Processing time vs memory usage
• Complexity 
• Talked about micro controllers
• Raspberry pi pico is really fast and really cheap
• Forza LED Strip Tachometer https://www.youtube.com/watch?v=_tIw8-Gl2F4 
• Java script
• this
• is fun, what is the scoping and semantics
• Functional vs OO javascript vs ???
• ??? may be procedural
• Lesson learned: “There is no substitute for Integration Tests”
• again
• This was not on Conway’s game but in real life.

Code & Coffee recap from 8/6/2021

 Topic: Conway’s Game of Life Challenge

• Keeping up with tech
• is important
• or tech will leave you
• Programming is hard: Copy all the elements of an array
• for (m=0; m < len; m++) {
• for (n=0; n < len; ++n) {
• will it work?
• no.
• BOO!
• This was an example problem and fragment of one person’s solution
• This was a rough conversation.
• Sometimes it takes a bit for things to click, sometimes they don’t
• These conversations should be handled gracefully with an eye towards everyone’s future.
• Some people are more wired for programming
• Missed a lot of stuff about containers and networking and latency
• And I was driving Sam so I missed taking notes
• But it was good stuff
• Bruce was talking about Native Spring
• Sounds pretty cool, lots of potential
• Make sure you have tests it sounds like there is some tree shaking going on during the running of the tests and if you don’t use a class in a test it might not notice that you need things compiled in to work.
• Talked about the intersection of computerized processes and how they interact with the real world.
• Do you know what the price is.  Really?
• Introduced the “Conway’s Game of Life” challenge
• Do an implementation
• Bring something to talk about related to the implementation next week
• Or if you won’t be attending, then send your implementation and we will talk about it, just let us know if we should be nice or rip it to shreds.
• Challenge detai: https://docs.google.com/document/d/1vHoERSQq-9gwYb10ff6XzipnbaVzQHzN0JcJt8vmu-k/edit?usp=sharing

Code & Coffee recap from 7/30/2021

 Topic: "What are you reading"  60 second review and bring links to share if you are able.

This week we talked about what we are reading or looking forward to reading soon.  I find this to be an expensive topic as it tends to add more to my bookshelf.  Good discussion and lots of variety.

Thomas:

• Segueing into management-is books:
• Drive by Dan Pink
• “this could be four blog posts and two ted talks and were done ;-)”
• But it is still very much worth the read
• Traction
• EOS 
• Effective Java
• 90 rules, did one rule per day
• Site Reliability Engineering
• Next up
• Head First Design Patterns

Carlus:

• Managing the Professional Service Firm
• Carlus’s review: “I am leaning more on the Manager style books right now.  Here is one that I am actively working on.  First part is excellent....later chapters most people find a little more dry....but there are still some great nuggets”
• https://www.amazon.com/Managing-Professional-Service-David-Maister/dp/0684834316/ref=sxts_rp_s1_0?crid=18EAPSCT2P3JG&cv_ct_cx=managing+the+professional+service+firm&dchild=1&keywords=managing+the+professional+service+firm&pd_rd_i=0684834316&pd_rd_r=8c66ee42-e588-4ad4-9d19-cd9adda23081&pd_rd_w=H7CE4&pd_rd_wg=lZwjR&pf_rd_p=c6bde456-f877-4246-800f-44405f638777&pf_rd_r=W26W22AGVHF0WHJS1JAK&psc=1&qid=1627649867&sprefix=managing+services%2Caps%2C155&sr=1-1-f0029781-b79b-4b60-9cb0-eeda4dea34d6

Hoppe:

• In progress:
• Better Decisions, Fewer Regrets: 5 Questions to Help You Determine Your Next
• Mostly it is about 5 questions that can help determine how and why you are making decisions
• https://smile.amazon.com/gp/product/B08657CF4L/ref=ppx_yo_dt_b_d_asin_title_o00aud_?ie=UTF8&psc=1
• Growing Object-Oriented Software, Guided by Tests
• Good stuff, some seems very fundamentally… but I think that is the point.
• There is a very good description and definition of the different types of tests that I am liking
• Unit test: A test that only tests code under your control
• Integration test: A test that tests a thin layer of code you control against external code
• Acceptance test: A business facing test that presents a piece of the application and show that it meets a business need.
• Typically is an end to end test, there may be reasons for it not to be but most of the time it will be.
• https://learning.oreilly.com/library/view/growing-object-oriented-software/9780321574442/
• On deck:
• Software Design for Flexibility: How to Avoid Programming Yourself into a Corner
• https://mitpress.mit.edu/books/software-design-flexibility
• This is related to and perhaps a next step after Structured Interpretation of Computer Programs which is also on deck and should likely precede this:
• https://mitpress.mit.edu/sites/default/files/sicp/index.html
• Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps
• This is a new release and looks to be very practical application stuff, looking forward to it.
• https://learning.oreilly.com/library/view/continuous-architecture-in/9780136523796/

Does this look interesting to you?  Let me know in the comments and I will get you invited to the slack channel where we organize the group.

Notes for Code & Coffee on 7/23/2021

Topic for 7/23: POP QUIZ:  Name a few code smells

• Identified smells:
• Player 1 - (anonymized players in case they prefer it that way)
• Overused singleton
• Overly complex test code (to get 100% coverage)
• test private ctor throws exception (Bruce’s example)
• Side effects
• Pushing to a dev branch that hasn’t been green in three months
• Broken builds
• See also disabled tests
• Player 2
• Lack of type safe code in Java
• extra tests required to assert types
• Git commit messages that just tell exactly what was done
• maybe useful maybe not
• “Undoing last commit”
• For better commits try:
• Arlo’s git notation
• https://github.com/RefactoringCombos/ArlosCommitNotation
• R!! rewrote everything
• Lack of tooling support (gitlab stinks, git log ftw)
• Do it intra story, then squash and merge
• Make it easy to make the change (this may be hard) then make the easy change (Kent Beck)
• Player 3
• Shotgun surgery
• Making one change causes need to change in other places
• Feature envy
• Got a function doing work and needs or over uses collaborators
• Long methods
• Badly named variables
• Player 4
• Inconsistent IDE linting settings.
• What to do about code smells
• “When I was at x-company that was our job”
• 2 million line code base
• 30% dead code
• 20% duplicate code
• Copy/Paste coding
• Aggressively adding huge amounts of dead code
• Removed dead code and worthless comments
• 5000 loc -> 400 loc (extreme case)
• Nothing makes me happier than deleting code
• Eclipse and Intellij
• if statements that explicitly compare against true or false.
• little t true and big true and other notes I missed
• Do some uncomfortable low risk cleanups
• Links:
• “Get a whiff of this” - Sandi Metz:
• About refactoring and code smells
• Recorded talk: https://www.youtube.com/watch?v=PJjHfa5yxlU
• Slides from the talk: https://speakerdeck.com/skmetz/get-a-whiff-of-this
• See slide 6 for the “Classic Smells”
• Slide 10 & 11 take and organize them into categories
• This looks interesting but have not tried it:
• https://sandimetz.com/99bottles
• Smells to refactorings cheatsheet:
• https://www.industriallogic.com/blog/smells-to-refactorings-cheatsheet/
• https://www.industriallogic.com/img/blog/2005/09/smellstorefactorings.pdf

 

Diode questions on the Amateur Extra exam

There was a question about diodes on the Amateur Extra exam and I wrote some notes, here they are for later reference in case I need them. 

 Here is a link to the question pool home which will give an idea of what to look into: http://www.ncvec.org/page.php?id=356 

Near the bottom of the page there is a link to diagrams: http://www.ncvec.org/downloads/2020ExtraClassPoolDiagrams.pdf 

And the question pool itself: http://www.ncvec.org/downloads/2020ExtraClassPoolJan22.txt 

 It looks like section E6B is the diode section but look at the other places that mention diodes too as that will show you other things you may be interested in. For instance there is a diode question in E6A that would be good to understand. This is only a start, the next step is to figure out the things that are unfamiliar, so look up the different types of diodes like Zener, Schottky, PIN, LED, sheesh there are a lot, this seems like a good start: 

https://www.watelectronics.com/types-of-diodes-applications/ 

 Check out the diagrams and see if you can identify all the diode symbols in Figure E6-2, then figure out what the application would be. 

 E6 is the circuit components section, good stuff to know for sure, but if it is a super rough section for you make sure to balance your study with the other sections where you are stronger and just give E6 your best shot. 

 Each section has an indication in the pool of how many questions will come from that section. E1A was my nemesis, memorizing the frequencies was just not working out... so I stopped worrying about it and figured out enough of them to get some right but even if I would have gotten everyone in that section wrong I would still be ok (and I have a handy chart to look them up for when I do need to know: http://www.arrl.org/graphical-frequency-allocations)