Skip to main content
 

A must read. Too many quotes to pull, but I was glad to see Conceptual Integrity and Behavior instead of Features included.

https://doriantaylor.com/agile-as-trauma

What if the Agile software movement was the manifestation of an entire industry that was, just, like, dealing with some stuff right now?





 

Kent Beck would not approve of calling hot desks "Agile Seating"...





 

Dark Agile and the importance of making space for diversity.

https://martinfowler.com/articles/agile-aus-2018.html





 

Come Home Paul! Come Home!

- First time I've seen Recruiters targeting expat folks. What next, will they contact my family to put pressure on me to move back?
- Including a Youtube video in your emails is a good way to get your message visibility in Inbox. Even if it's this dorky thing.
- It also appears that Target makes it's recruiters use their DJ name. In da house with *DJ Luke Doubler* and his sidekick *Talent Scout*.

http://rumandmonkey.com/widgets/toys/namegen/3675

---
Paul,

My name is Luke Doubler and I’m a talent scout for Target Corporation.

I’m reaching out to you because I see that you went to the U of M and I’d like to see if you’d consider coming back.

I found your name on your GitHub profile (http://github.com/lindner) and see you are a full stack developer with contributions in JavaScript, full stack products, Apache, Amazon Dynamo and others. I also see via your LinkedIn profile you are with Google. I’d like to see if you’d consider a leadership role with Target.

Our corporate office located downtown Minneapolis has an engineer leadership position open in a very agile/scrum development team building products that will propel Target.com as the premier online retailer.

Would you be open to connecting Paul via phone? Your full stack development experiences appears to be exactly what we’re seeking. I can make myself available based on your schedule.

I look forward to connecting.

https://www.youtube.com/watch?v=QopMlVsPH3Y

 

Nuggets of truth in there.

Favorite one so far is _"If it takes you too long to refactor than you are not refactoring enough."_


http://www.agile-process.org/proverbs.html






 

Life At Hi5

So far so good. On the right you'll find a leftover from the previous occupant of my space. It's been over 2 years since my last job change, so I forgot about how much work it is to get integrated into a new environment.  Adding 30+ IM contacts, updating the address book, setting up the laptop, getting e-mail just so, etc. 

Adding to that is jumping into a very different environment.  There's lots to like and lots to learn.  So far I'm getting up to speed on:

  • Perforce (instead of subversion, cvs, etc.) -- looks powerful and clunky at the same time.
  • Jira - this is very cool.  It combines bug tracking, agile sprints, and a wiki all in one.  It's mediawiki, trac, RT, and FogBugz all in one.
  • SuSE SLES 9 - With the infamous ReiserFS filesystem.  Give me yum over YaST anyday...
  • Hyperic HQ - Nagios+Cacti+much more.  Includes autodiscovery and can automatically restart services when they fail.  So very nice.
  • Zeus as a frontend to redundant memcaches.
  • Java Resin/JSP/JDBC/Eclipse/...  less said the better.


There's lots more going on here than you'd think.  A bit strapped for time at the moment -- will blog more soon...


 

Bay XP Meeting Roundup 8/23/2006

BayXP (The Bay Area Extreme Programming Group) had a small meeting at the offices of ThoughtWorks here in San Francisco.  The topic was interesting things learned at the Agile 2006 conference.

I found a number of items to add to my reading list, Including Refactoring Databases and Working Effectively with Legacy Code.  (See Links below)

Topics of discussion from the meeting included

  • Coding Dojo - how to get hang of test-first development and Pair programming.
  • A lot of talk about how Rails stacks up against upteen different Java Frameworks.
  • The TDD Pair Programming Game is an interesting way of pairing that seems to make sense.  It's like a dance.  I write a failing test, you implement, then I refactor, then you write a test, etc.
  • The best name for a talk that I've seen in a long time was Crushing Fear Under the Iron Heel of Action.  It explored how to deal with team dynamics in an Agile environment, mostly by saying "What's the worst thing that can happen". 
  • Found out about a web site called Developer Testing.  Another thing to add to the RSS reader...
  • There was a short talk about Code Debt.  Some people are surmising that Code Debt should be publicly disclosed in a companies SEC S4 forms via Sarbanes-Oxley.  One interesting quote was that code is an asset and you should maintain that asset properly because assets "increase the means of production".  If you don't maintain code properly and use correct process your software becomes a liability.  (Or course that begs the question of who defines the Generally Acceptable Coding Practices (GACP!)