Daniel has moved

@tastapod
129 Followers
213 Following
597 Posts
Moved to @tastapod
[announce] Support Twist as announcer · Issue #1662 · jreleaser/jreleaser

Developer API docs can be found at https://developer.twist.com/v3/#introduction

GitHub

For everyone up in arms about #slack, I can recommend #twist by Doist (the Todoist people). Underrated, “calm” version of async chatops.

https://twist.com/

Twist: Organized work communication for flexible teams

See how much more efficient your teamwork can be (even across time zones). Named a World Changing Idea by Fast Company.

Twist
I’m just saying.
Hey @tastapod, I've been recently watching some of your conference talks on YT, namely "Beyond Features", "CUPID - for joyful coding", "The most dangerous phrase" and "How to break the rules".

Coming from a Software Engineer perspective, trying to understand the business side beyond tech dogma and to make sense out the struggle we are in as an industry, it's been extremely valuable.

Thank you.

TIL:

% idea diff dir1 dir2

Thanks JetBrains!

Who at #Apple decided that these were acceptable colours for road name text and do they know anyone over the age of 23?
Refactoring is a normal part of software development, and it's useful to get more fluent with changing your design safely. Fluency comes from practice, and my latest video is designed as a team learning session to make the practice more effective *and* more fun. You'll work on an everyday design change - converting from a class/static method to an instance method. https://youtu.be/sngRW3zPiiE
Unlock the Power of Refactoring in Everyday OO Design | Team Learning

YouTube
@JeffGrigg which is great! Though because BDD has become something more--with its own tools and practices and delightful whole-team approach--I feel the need to make a distinction between "human-readable scenario" and "detailed developer specification." When we dig into it, BDD and TDD are incredibly similar wrt the skills necessary to do them well, yet they address different human needs around software development.

Security teams and site reliability engineers (SREs) are natural allies in the fight against randomness, terrible systems, and how those systems can hurt people and give us yet another reason to hate surprises. We want 90% of the same thing -- and both of us can use this to our advantage.

(Many thanks to SREcon, who invited me to speak about this.)

https://www.darkreading.com/cybersecurity-operations/security-teams-sres-want-same-thing-lets-make-it-happen

Security Teams & SREs Want the Same Thing: Let's Make It Happen

Site reliability engineers (SREs) and security teams are more powerful when they work together, and being able to combine our efforts can make or break our teams' experiences and outputs.

know your bees