Great collection of guidance on async/await programming patterns and antipatterns compiled by @davidfowl - definitely qualifies as Must Read® https://t.co/tZJWSL2oyz
Das bbv #bbvgathering war auch 2018 ein Erfolg. Danke allen SpeakerInnen und WorkshopleiterInnen, dem O-Board und dem gesamten @bbvch Team für die lehrreichen, spannenden und intensiven Tage in Berlin!
@mj_richardson_@OctopusDeploy whit this step template it would be great to browse the available nuget package versions to choose one. otherwise I have to guess which versions are available. But I'll find a solution!
@mj_richardson_@OctopusDeploy this is not an option because of multiple environments. At this point I don't know on which env it will be deployed, except if I could do conditional releases based on the package version (1.0-unstable -> DevEnv; 1.0-beta -> Staging). I think I go with the chain deployment!
@OctopusDeploy there exists a "Deploy a release" step template but i'm missing a "Create a release" step. Should I use octo.exe as a workaround or is there a step which i can use?
repeat after me
Code not shipped is dead code
Code not shipped doesn’t exist
Code sans prod is just a toy
Code without users isn’t real
Code with test data hasn’t been tested
Code without net doesn’t matter
Code without prod is worth zero fucks
finna tattoo this shit on someone https://t.co/q89KCOVlg7