Code & Coffee 4/8/2022

 Code & Coffee 4/8/2022

• Meetings!
• Why so many
• Looking for 
• Example
• Meeting about a service
• Dev team was attempting to create an unauthenticated service with no ssl
• Meeting was to discuss that
• How did that come to be?
• Meetings turned into Authentication and security
• Why is it acceptable to create an unauthenticated unsecure service?
• Is there training needed?
• Oauth and JWT?
• JWT / jot what are you talking about?
• it is suggested in rfc7519 to pronounce JWT as "jot"
• https://datatracker.ietf.org/doc/html/rfc7519

Is it safe to store JWT in memory?

To reiterate, whatever you do, don't store a JWT in local storage (or session storage). If any of the third-party scripts you include in your page is compromised, it can access all your users' tokens. To keep them secure, you should always store JWTs inside an httpOnly cookie

Code & Coffee - 4/15/2022

 Code & Coffee - 4/15/2022

• Slack hacks and tools
• Organize channels into groups
• Google calendar integrations
• What happens when a Saas goes down
• Risk assessment
• -- insert link from Derek
• Jira
• use a spreadsheet for a couple days?
• Git
• It is distributed, don't panic
• Might want more than an "accidental strategy" though
• Regular mirroring of code repository
• Mirror the pipeline enough to do an emergency build
• AWS
• panic!
• CI server
• What happens when the pipeline provider zonks out?
• Can you do a local build and deploy?
• What parts can be skipped?
• Soft deletes
• Safer removal of data by soft delete first
• Soft deletes and right to be forgotten laws
• Don't recognize me list
• how to store the list?
• Wouldn't the list turn into a high value target
• Or do would it be stored as a sort of fingerprint

Code & Coffee - 4/22/2022

 Code & Coffee 4/22/2022

• Office upgrades
• Warming up the floor 
• Heated floor
• Or a nice thick rug!
• what about the rolly chair?
• Hang it from the ceiling
• Random stories
• It's a good thing our dads didn't present a bull for the damages we caused
• Working in Clojure
• Catching up on who is where and how things are going
• Worked with so-n-so for a couple years and saw him once even though we worked 20 ft apart.
• different floors
• Interview with a javascript developer:
• https://www.youtube.com/watch?v=Uo3cL4nrGOk
• Great Adventure dating book:
• https://www.theadventurechallenge.com/
• How to feel old
• The new intern was born after I got married
• The 20th anniversary edition of Tron is now 20 years old.
• Coding challenge
• Simulated PR in Github
• How does the candidate respond to critical and positive feedback?
• Unlimited time (days)
• Differentiating developer level
• Juniors talk about what happened around them
• Mids talk about what happened in the project
• Seniors talk about their contribution and the value to the business
• Super Seniors talk about everything
• Thomas wore a tie
• How much cloud development/serverless can be done locally
• Quite a bit but it gets complex
• Cross cloud portability
• Sticky platforms
• Sometimes monoliths are not so bad:
• https://www.amazon.com/Strategic-Monoliths-Microservices-Addison-Wesley-Signature/dp/0137355467
• Unit tests are crap:
• Try this to improve:
• https://www.manning.com/books/effective-software-testing
• This talks a lot about how to better structure tests for good results.

Code & Coffee - 4/1/2022

 Code & Coffee - 4/1/2022

• Looking for moar developers - writing the job description
• Checked out some code and talked about Java Optional for a bit.
• fiddled with the code and made it betterer
• Code review is a view into the heart and soul.... or at least thought process of how other developers think
• Ahh yes, today is the day to be a little extra careful on the internet
• What is your favorite April Fools internet thing?

Code & Coffee - 3/18/2022

 Code & Coffee - 3/18/2022

• Data migrations
• Learning about your data
• What database to use
• Datastore vs. CloudSQL vs. Spanner
• advantages, disadvantages and differences
• Bringing data over and comparing to make sure the data is ok
• Streaming data
• 30 minute migration vs 2 weeks
• 1000 vs 400 million records
• Unit tests
• Why
• Independent/Isolated
• Descriptive
• Using good method names
• "networkchuck"
• makes it fun to watch.

Code & Coffee - 3/25/2022

 Code & Coffee - 3/25/2022

• Weekend plans
• Epic pillow fort in the living room
• Helping with ham radio test session
• Kids and cars
• Some are less interesting in driving
• But get there eventually
• Picking a car for kids
• Learning by fixing
• Are we in the middle?
• Grandma and Grandpa didn't know how to program a vcr
• The kids don't either
• Is that really a problem
• They need to know how to mop, or use a broom
• The generational oscillation effect of skills
• Diy - do it yourself - has the skill to do
• difm - do it for me - someone else will to it for me
• skilled trade - but cobblers kids don't have shoes
• repeat
• Balancing diy and difm
• Pulumi vs Terraform
• Terraform vs Terraform Cloud & Enterprise
• https://www.pulumi.com/docs/intro/vs/terraform/
• Thermal pad replacement 108 to 96 degrees

Code & Coffee - 3/4/2022

 Code & Coffee - 3/4/2022

• How to properly spectate at a cross country event
• Cheating is ok for parents ;-)
• Topic of the week: Spring cleaning
• Cleaning out the tech debt
• CI/CD betterization
• Better deployments with Ansible
• Better branching strategy
• Tag the production branch
• First admit that there is a problem
• Checking with the sr engineers about what problems there are
• Roadmapping the items - seeking funding for low hanging fruit
• Maintenance
• Documentation
• Database change management
• Tagging git repos as things are deployed
• The batman will answer the call
• Retraining the production support requesters to use the bat-signal
• Developers are happier not
• Watch out for the Velociraptors
• They sneak in and eat your velocity
• Over optimization
• Pike 5 Rules
• https://users.ece.utexas.edu/~adnan/pike.html
• Hoares Maxim
• In the summary of the Pike rules link
• What is success for the tech debt exercise?
• Response:
• Better automation
• Sonar runs against the code
• unit tests with some coverage
• Challenge:
• Inspire the team members to:
• Identify tech debt
• Start taking steps to remediate the tech debt
• This is an indication of growth of the members of the team
• Time to clean up the passwords in the source files
• -- anonymous
• It ain't easy to nuke passwords from github, change the password and don't commit any more passwords to github
• "I need you to fail, so that things get better"
• Oh and no more working until 4am
• Cleaning up the home theater after the raid failure
• BackBlaze saved the day the raid was backed up and the content was saved offsite
• https://www.backblaze.com/
• Icedrive is an alternative: https://icedrive.net/

Good stuff as usual, thank you to all for stopping by.