Category: Uncategorized

This is a test

πŸ›ŒπŸ©β€Β  Β  Β πŸ’¨πŸ§‘πŸ›€πŸ‘οΈβ€πŸ—¨οΈβ€πŸ’¬πŸ›Œ
πŸ©πŸ–€πŸ’›πŸ›€Β  Β Β  πŸ’šπŸ’¬
πŸ•ŠπŸ’›πŸ’¬πŸ›ŒΒ  Β  Β πŸ’­β€πŸ€–πŸ–€πŸ›€β€
πŸ›ŒπŸ©β€Β  Β  Β πŸ’¨πŸ§‘πŸšπŸ‘€.

Tips on Organising Hack Days / Hackathons

Caroline on Twitter asked “Currently researching “how to put on a data hack day” Any tips?”

Here is my very notey response, mostly based on my experience as (a) participant at HackΒ  Manchester (RIP) and (b) being a judge myself at various different events over the years.

  • Think about the comfort of the participants – both physical and emotional.
  • How can you be welcoming and supportive?
  • Give them the opportunity to solve real-world problems but with a lot of scope for creativity.
  • Give them a choice of different challenges.
  • Don’t expect judges to do full code reviews (too time consuming) – judge by presented results instead.
  • Ask participants to present their results in an easy to digest format (to streamline the judges’ job).
  • Let people present vision as well as working results (it’s hard to get things fully functional in a short space of time).
  • Recruit helpers to give a hand when participants are stuck.
  • When recruiting helpers, emphasise they do NOT have to know all the answers. Their job is to help people seek solutions, not provide solutions themselves.
  • Have a v strict time limit for final presentations. How many teams do you have? How long will presentations take overall if (eg) you give them 2 mins each and allow extra for changeovers? Is that too much?
  • You’ll be surprised how much people can present in even 1 min. Let them know in advance that time limits will be strict. Cut them off if they overrun.
  • One great approach if you have a v big event is to get them to create a 1-min video each, to be watched separately by judges.

SDDConf May 2022 – Compassionate Refactoring

Part 1 – Refactor Tennis1

git clone https://github.com/emilybache/Tennis-Refactoring-Kata.git

Choose your language

Refactor TennisGame1

Part 2 – Example of unit tests retrofitted

Either… git clone git@github.com:claresudbery/gilded-rose-kata.git

or… git clone https://github.com/claresudbery/gilded-rose-kata.git

(if in doubt choose the second)

cd gilded-rose-kata

git checkout csharp-test-start

Look at this file for description of problem (GildedRoseRequirements.md in root of repo)

Look at this file to see tests (/csharp/GildedRoseTests.cs)

Part 4 – Easier to understand / cheaper to modify

Demo 1 – Easier to understand / cheaper to modify

Part 6 – Extract Method

Demo 2 – Extract method

Refactoring catalog

Part 7 – Refactoring tools

Demo 3 – Refactoring tools

All Parts – Sticky notes from Walls

All visible here

Part 8 – Further resources and ideas

New Domain Host – Subscribers Moving

I’m about to move subscribers from the old domain host to the new one. The url remains the same, it’s just that the domain is now self-hosted.

Email subscribers will continue to receive email notifications of new posts as before, but WordPress.com followers will only see new posts in the Reader. They will not receive email updates unless they subscribe to receive those on the new site, which they can do via the Subscriptions widget at the bottom of the sidebar.

Hello

Hello

I’m a bear of little brain, and when I encounter a concept for the first time I need it to be explained in simple terms with very clear examples. If I can’t find such an explanation, I will attempt to write it myself and place it here.

Sometimes even if I do find a simple summary, I’ll re-explain it in my own words to consolidate my own understanding.

I make no claims for the accuracy of my understanding, and I welcome corrections and clarifications in the comments box.

With thanks to Martin Fowler, who suggested I write this blog.

I’m going to start by copying in notes I have made recently on various things, so there will be a flurry of posts to start with… and then who knows what’ll happen?