[javaone 2025] Fallacies of Software Development

Speaker: Nathaniel Schutta

See the table of contents for more posts


Note: This is not a live blog. I took notes during the session and posted this after as I was expecting a phone call. Also, I missed the last 10 minutes for said phone call.

  • Architect as a service 
  • We like to reinvent the wheel
  • We take for granted people know what we know. Ex. New people haven’t heard of Gang of Four book
  • Answer to many things is it depends 
  • Often seems insignificant in the moment. Find out later matters. Patterns help with this 
  • Software has similarities. Got tired of putting a front end on a database   Will always be doing app modernization 
  • Learn from parents mistakes   Save time. 
  • Higher bandwidth conversation when use words like facade
  • Humans have patterns too
  • NIH. Not invented here. Not my idea 
  • Think can build better than off the shelf. Usually not true but sometimes is   Focus on differentiator.  Politics. Turf war. Jealous/budget
  • Meta work is more interesting than the work 
  • Some people need spotlight. Arsonist firefighter  not a zero sum gene. Goal is to make better software. 
  • Some people missed sharing and golden rule in kindergarten 
  • Value if created something. People valued resale at 63% if built ikea item 
  • Dangerous “that’s how we’ve always done it”. Counter with asking if has to be that way 
  • Status quo is free. What does it cost. Opportunity cost?
  • Are customers proud of hand rolled project 
  • Wouldn’t get on a plane if no maintenance in last year. 
  • Great presenter. Visuals. Quotes. Few words per slide 
  • Sunk. Cost fallacy. I had pizza for lunch. Might as well have an entire cake for dinner 
  • Ok to ask why something is. New hires will notice. Others used to seeing it 

My take

I’ve seen him speak before and he is excellent. Good visuals/few words on a slide/excellent pace and storytelling

using word and floating images to add my new book to my resume

Every year I update my resume. This year, I got to add “Real-World Java: Helping You Navigate the Java Ecosystem!” It’s for

  • Those who know the syntax/language, but not the whole ecosystem
  • Students
  • People transferring from another language.
  • People who haven’t worked with Java in many years
  • People on legacy projects

For many years I’ve had the cover of my book and some certification badges on my resume. I had them as individual images up until now. This time I wanted to do better because I wanted the covers to be aligned.

Making the image

I used PowerPoint to align the images. (I also have Keynote on my computer, but PowerPoint was open as Victor and I are using it for our upcoming presentation at the NY/Garden State Java User Groups and DevNexus. Both tools make it easy to align images. I then did a copy and paste special to get a PNG of this is as one big image.

Note: We do not make images for the cert book this ways. Scott made all those images using a proper image editing tool.

Getting it in Word

When you paste into Word, it automatically inserts it into the text. I didn’t want that. I wanted more control.

Instead i right clicked the image and choose Wrap text > In front of text. Then I dragged it to where i wanted.

How it looks

Here’s how the section of my resume for the stuff I don’t do for my employer.

PASSED! Jeanne’s Experience Taking the SAFe ScrumMaster exam.

Today I took the SAFe 6.0 ScrumMaster certification and passed with a score of 80%. Passing is 73%. I was optimizing for passing quickly and not investing a lot of time rather than a high score though.

My path to certification

As background, I’ve been a part time SM (and rest of the time developer) for over a decade and been on a SAFe team for a while.

  • Oct 21-24 – took SAFe6 training course – half a day each of the four days. It was online and I felt myself absorbing less each day. It’s hard to pay attention to people talking online for that long every day. I also felt the energy level of fellow students dropping both in the main classroom and in the breakouts. Which became a negative feedback loop.
  • Oct 24 – I was also helping get ready for a conference so my brain was somewhat distracted
  • Oct 25-27 – went on vacation. Didn’t think about SAFe or work at all
  • Oct 28-29 – attended/spoke at/helped run an agile conference. Further distanced myself from class with more information on the topic of agile that wasn’t safe.
  • Oct 30 – went to NYC Scrum user group. Awesome talk but again more info on the topic of agile that wasn’t safe. Took first practice test when I got home (and was tired.). Got at 80%. Good enough. it’s a pass.
  • Oct 31 – re-read PDF from class and then took real exam in between trick or treaters. Tired and distracted but glad to be done. Pass!

In class they advised us to practice until getting a 90% on the pracitce exam. I did not follow this advice. It’s only $50 for a retake so better to try the real one and see what happened rather than

I didn’t want to leave this for the weekend because I want to spend a bunch of time working on my upcoming book so need to be thinking about Java. Also, you have to take it within 30 days and I’m not going to find myself with more time if I wait.

The exam

All questions were single answer multiple choice with four possible answers. All of them were relatively short which was a pleasure after my experience with the Java 21 exam!

Some were very easy. Some had two reasonable sounding answers. For a number of them you had to know how SAFe would handle the scenario even if that’s not how another agile framework would.

Logistics

The exam is non proctored and you don’t have to show your environment on camera. It was nice not to have to clean up all the programming books and papers around me. The environment is exactly the same as the practice tests one.

After the exam

You get a score report with the % right for each category. This part looks like the report for the practice exam. Unlike the practice exam, you don’t see the questions and which ones you got wrong specifically.

Timing

As I mentioned in my experience with the Java 21 exam blog, I typically finish exams with lots of time to spare. This was a 90 minute exam. I finished my first pass in 34 minutes and my second (to clean up the ones I was unsure of) in 20. really a little less sinceI got up for trick or treaters a few times.