peitor

How product engineering teams avoid dependencies -- the independent executor model
2021-11-06



What is the Independent Executor model?
It is natural to need things from other teams. It can be tempting to wait for them or depend on them to provide something for you. This happens because they own the area you need to do work in.

For example, you might need a team to add a field into their API. Or you might need them to build a new API for you. Sometimes without these changes, you can’t deliver what you need to.

peitor

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.

That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.

peitor

From time to time, Musk will send out an e-mail to the entire company to enforce a new policy or let them know about something that's bothering him. One of the more famous e-mails arrived in May 2010 with the subject line: Acronyms Seriously Suck:

There is a creeping tendency to use made up acronyms at SpaceX. Excessive use of made up acronyms is a significant impediment to communication and keeping communication good as we grow is incredibly important. Individually, a few acronyms here and there may not seem so bad, but if a thousand people are making these up, over time the result will be a huge glossary that we have to issue to new employees. No one can actually remember all these acronyms and people don't want to seem dumb in a meeting, so they just sit there in ignorance. This is particularly tough on new employees.

That needs to stop immediately or I will take drastic action - I have given enough warning over the years. Unless an acronym is approved by me, it should not enter the SpaceX glossary.

peitor

Video recordings of my talks

Innovation through Scrum + Continuous Delivery https://www.youtube.com/watch?v=TMyhhuQPEow

Clean Code, Testing and Continuous Improvement with Peter Gfader https://www.youtube.com/watch?v=4CAGaopAEew

How to Achieve Continuous Delivery with TFS https://www.youtube.com/watch?v=fLG1yk2ZyJM

peitor

Whitepaper: Use Scrum + Continuous Delivery To Build the Right Thing https://www.scrum.org/resources/use-scrum-continuous-delivery-build-right-thing

http://personalretro.tumblr.com/

http://copycat.apphb.com/

http://twitterfish.apphb.com/

peitor

REM Don't use this in Production!
REM Think about switching from MsDeploy to "MS Release Management" or even better: "Octopus Deploy" https://octopus.com/
REM ----------
REM In order for this to succeed:
REM   * Run MsDeploy service on target machine
REM ----------
REM Writes log file to history.txt
REM On Success: Copies .zip files to Archive folder for later deployment

REM --------------

peitor

    /// <summary>
    /// Fixes all DateTime and DateTime? properties to be datetime2 in SQL Server.
    /// from http://flashfm.blogspot.ch/2011/11/entity-framework-41-code-first-fixing.html
    /// </summary>
    public static class ContextUtils
    {
        public static void FixDateTimeColumns(DbContext context, DbModelBuilder modelBuilder)
        {
            var contextProps = context.GetType().GetProperties(BindingFlags.Instance | BindingFlags.Public);
            foreach (var contextProp in contextProps)

peitor

------------- Start of calc.cob ---------------------------
       IDENTIFICATION DIVISION.                                 
       PROGRAM-ID.  CALC.                                       
      *AUTHOR.      R. HAENGGI.                                 
       ENVIRONMENT DIVISION.                                    
       CONFIGURATION SECTION.                                   
       SPECIAL-NAMES.                                           
           TERMINAL IS BILDSCHIRM.                              
       DATA DIVISION.                                           
       WORKING-STORAGE SECTION.                                 

peitor

Programming Achievements: How to Level Up as a Developer

This gist is part of a blog post. Check it out at:

http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
[X] = my dones

peitor

void UpdateQuality()
        {
            for (var i = 0; i < Items.Count; i++)
            {
                if (Items[i].Name != "Aged Brie" && Items[i].Name != "Backstage passes to a TAFKAL80ETC concert")
                {
                    if (Items[i].Quality > 0)
                    {
                        if (Items[i].Name != "Sulfuras, Hand of Ragnaros")
                        {