Graeme Lindsay retweeted
Was asked what I don’t like about Scrum. Not much, really. Just:
• Backlogs
• Sprints
• Daily Scrums
• Sprint Reviews
• POs
• SMs
• Commitments
• Accountabilities
• Standardization on an inflexible framework
• Certs
Just little stuff like that. The rest is okay.
Graeme Lindsay retweeted
I’m not a fan of giving experienced Staff engineers coding interviews.
Why?
If you’ve made it to this level, either you can code well, or you’ve learned to solve technical problems using your other muscles.
The outcomes are what matters.
Loved this passage from @whereistanya
The early stages of the SW career phase can be so fixated on coding, which really is a small part of what it takes to be an Engineer. Seniority in Engineering requires the soft skills to understand ‘why’ before coding…
Really interesting thoughts from @Lethain on dealing with the ambiguity of senior and leadership roles in Engineering.
Defining your personal mission is one of the biggest challenges when transitioning into a new leadership role - from an IC role or leadership in another org.
Yet another great interview passage, this time from @Lethain on:
The Core Challenge of Engineering Leadership Roles & The Three Most Common Leadership Pitfalls of Staff+ and Director+ People.
<Link at the end>
🧵🧵🧵
Graeme Lindsay retweeted
🔥Hot off the press: Issue #137 of Level Up, a curated newsletter for leaders in tech #cto #vpeng #engmanager #techlead w/content from @kinlane @lilyhnewman @firstround @FosterLearning @graemelind & more! See levelup.patkua.com/archive/1…
A fantastic review of the BBC’s serverless web platform, WebCore, after a year of operation - by Johnathan Ishmael (@Mirdin)
link.medium.com/E4s0SUepTob
Platform-as-a-strategy: For the past 2 years I’ve been a part of the BBC’s web tech strategy to build a platform and shared capabilities. This is a post about lessons I’ve learned on the link between the shape of the organisation and the shape of the tech
medium.com/bbc-design-engine…
Graeme Lindsay retweeted
Would you like to do a postgraduate apprenticeship in my department, working on our design system and our back-end business layer platform? careershub.bbc.co.uk/members…
Graeme Lindsay retweeted
Our BDD series books (Discovery & Formulation) will be available on Kindle for £0.99/€0.99/$0.99 each this weekend.
The sale starts on Saturday morning (European time) and will run until the end of the weekend.
Bddbooks.com
@gasparnagy
Graeme Lindsay retweeted
"While I’m not here to argue that coding interviews are entirely broken (though others have), I strongly believe that they have no place when interviewing senior engineers."
tinyurl.com/yxckj4je
Graeme Lindsay retweeted
Missing campus? Let’s build it ⛏
This Friday we are launching #CraftUofG – a Minecraft server which will be free for all @uofglasgow students & staff to join 👏
The plan is to build the Gilmorehill Campus inside the game!
Find out more & sign-up ➡️ bit.ly/CraftUofG
Graeme Lindsay retweeted
Backlog refinement (not "grooming") is an ongoing process, not a meeting. Put a Story Map on the [perhaps virtual] wall and look at it occasionally. When something new comes along, put it on the wall in an appropriate place. If you need a discussion, discuss right then.
Graeme Lindsay retweeted
Why do smart product people & teams often build products with mediocre or no impact?
A cautionary thread of biases and fallacies we encounter when building products👇🏾
1/10
Graeme Lindsay retweeted
Another day as a professional developer.
I'll be balancing some binary trees, implementing bubble sort and FizzBuzz a few times, then I'll probably knock out a couple of quick fibonacci implementations.
All without using google or any libraries of course.
Graeme Lindsay retweeted
**THREAD**
The Daily Express has published an appalling, irresponsible and misleading weather article, giving the impression that ‘150mph winds’ will hit the UK this weekend.
Let me show you, with evidence, why this couldn't be further from the truth.
Graeme Lindsay retweeted
#Brexit
A View from Germany
Graeme Lindsay retweeted
Every time I make myself write out
We are doing _____
Because we see the problem of _____
We know it's a problem because _____
If we don't fix it, we'll see _____
We'll know we've fixed it when we get _____
the rest of the conversation/project/doc goes SO much easier.




























