The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,226 other subscribers

Archive for October 15th, 2019

Sprints, marathons and root canals and Brady Printed Lean Labels – for lean development

Posted by jpluimers on 2019/10/15

Apart from blank and custom labels, Brady also sells [WayBack] Brady Printed Lean Labels | BradyID.com

They work great for agile projects, despite marketed as “will help you improve reliability, up-time, and efficiency”.

I found them via:

 

which led me to [WayBack] Sprints, marathons and root canals, which is a long but recommended read.

That got me to a book that is now on my reading list: [WayBack] James Shore: Agile-Book, especially this chapter:

[WayBack] James Shore: The Art of Agile Development: Iteration Planning

 

Assorted sets of stickers are (all in packs of 10 each):

[WayBack] Brady Part: 110762 | Assorted Lean Stickers

[WayBackBrady Part: 110763 | Assorted Reliability Stickers

 

Though you can also get them individually in 10 packs:

Read the rest of this entry »

Posted in Agile, Conference Topics, Conferences, Development, Event, Software Development | Leave a Comment »

IBM 1980 Pascal manuals

Posted by jpluimers on 2019/10/15

Just found back an old note with Pascal manuals for the IBM 370 machines: the Reference Manual and Programmers Guide.

–jeroen

Posted in Development, Pascal, Software Development | Leave a Comment »

Design Patterns aren’t the goal, especially if you can cover the pattern with a language feature

Posted by jpluimers on 2019/10/15

Interesting read: [Archive.is] Are Design Patterns Missing Language Features.

On various places, it has been claimed that use of DesignPatterns, especially complex ones like VisitorPattern, are actually indicators that the language being used isn’t powerful enough. Many DesignPatterns are by convention rather than encapsulable in a library or component, and as such contain repetition and thus violate OnceAndOnlyOnce. If it didn’t contain at least some repetition, or something that could be Refactored out, then it wouldn’t be a pattern.

When applying design pattern, always remember that back then the Gang of Four wrote their book, languages were less powerful than now.

So always check if a design pattern cannot be applied by using a feature of the language you are using.

Examples from that page:

A list of DesignPatterns and a language feature that (largely) replaces them:

 VisitorPattern  .............. GenericFunctions (MultipleDispatch)
 FactoryPattern  .............. MetaClasses, closures
 SingletonPattern ............. MetaClasses
 IteratorPattern............... AnonymousFunctions 
              (used with HigherOrderFunctions, 
               MapFunction, FilterFunction, etc.)
 InterpreterPattern............ Macros (extending the language)
               EvalFunction, MetaCircularInterpreter
               Support for parser generation (for differing syntax)
 CommandPattern ............... Closures, LexicalScope, 
               AnonymousFunctions, FirstClassFunctions
 HandleBodyPattern............. Delegation, Macros, MetaClasses
 RunAndReturnSuccessor......... TailCallOptimization
 Abstract-Factory,
 Flyweight,
 Factory-Method,
 State, Proxy,
 Chain-of-Responsibility....... FirstClass types (Norvig)
 Mediator, Observer............ Method combination (Norvig)
 BuilderPattern................ Multi Methods (Norvig)
 FacadePattern................. Modules (Norvig)
 StrategyPattern............... higher order functions (Gene Michael Stover?), ControlTable
 AssociationList................Dictionaries, maps, HashTables
                    (these go by numerous names in different languages)

Food for thought…

–jeroen

Posted in Design Patterns, Development, Software Development | Leave a Comment »

 
%d bloggers like this: