Sebastian Gebski

Sebastian Gebski

Geek, agilista, blogger, codefella, serial reader. In the daylight - I navigate & lead software engineering. #lean #design #aws #elixir #analytics. I speak here for myself only.

Check out the latest posts

State pattern, tech debt fertilizer

A short post about unreasonable usage of State pattern [https://en.wikipedia.org/wiki/State_pattern] - something I keep seeing every so often in code (regardless of language / platform). What's a State pattern? State pattern is a way to encapsulate state (& behaviour that depends upon it)...

Weaving code like a boss - part II

Part I can be found here [https://no-kill-switch.ghost.io/weaving-code-like-a-boss-part-i/] Options considered By now, you should already have an overall idea what I was expecting of my new devmachine. What models did I consider to fulfill these needs? * I didn't consider MacBook Pro /w Retina [http://www....

Weaving code like a boss - part I

It's already over 3 months since I've swapped my primary code-crafting devmachine with Dell XPS 13 (2015) [http://www.dell.com/us/p/xps-13-9350-laptop/pd] - sounds like the high time for first conclusions & bold statements ^_^ -------------------------------------------------------------------------------- Before that, a brief clarification - I knew...

In defense of HIPPOs

The term HiPPO [http://whatis.techtarget.com/definition/HiPPOs-highest-paid-persons-opinions] ( Highest Paid Person's Opinion) is getting quite popular in project management world (& IT in particular) recently. What's the fuss about? When there's a decision to be taken & various options are discussed, people tend...

Ritualization - develop your good habits

Personally I'm a huge fan of information radiators [http://alistair.cockburn.us/Information+radiator] - I love the idea of full transparency & exposing vital, key information on continuously updated, automatically generated (from the single source of truth [https://en.wikipedia.org/wiki/Single_Source_of_Truth]) dashboards....

Few test-related tricks for (even) the old dogs

Just some random thoughts / stuff I've bumped into recently. Enjoy. Interweave tests in support I love this legacy code rule (it's supposed to help fighting the technical debt): > When you touch any existing piece of code, always leave it in at least slightly better shape...

You’ve successfully subscribed to No Kill Switch
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.