My Twitter archive of December 2018

In October 2022 I left Twitter. This is my tweet archive for December 2018.

Tweets

• My personal horror chart in @SmartBear's state of Code Review report: https://t.co/fKgOrao02M
• @Paratron @SmartBear Better than Jira or better than Office?
• Your #blockchain is most likely vaporware: https://t.co/XHuCe1bJ9M https://t.co/80ot0K9tE3
• I explained one of my #firstprinciples related to #git: Rebase and ideally Squash instead of Merge for Pull Requests https://t.co/vN25juxvkQ
• I think many developers shy away from rebasing because it regularly cannot be done automatically and you need a bit of practice to get used to a rebase flow and all it's interesting states (WTH is an empty commit?!). > https://t.co/5GhfxLS9Z2
• @Maxwell_Dev wrote a very good detailed guide on rebasing: https://t.co/pC2nrUQDK3 and even in there some of the more esoteric feeling things that can happen during a rebase are not covered. Learn by practicing this, and remember that you can always abort a rebase safely. >
• @Maxwell_Dev But if you are uncertain at first remember to save your branch before rebasing. If you push it to origin before a rebase attempt and you botch that rebase, you can do a git reset --hard origin/my-branch and everything is nice again ;-)
• @liran_tal I'm glad you liked it. It's currently more of a braindump without real structure, but I try to make a habit of going back to it every week or so.
• Here are some of the findings in the State of Code Review report ( https://t.co/dKacIsQi3T ) from @SmartBear that I found interesting. I currently do a lot of Code Reviews and the Recommendations for Your Team which the report provides at the end are good material! > https://t.co/lXWgVA4XZg
• (p. 7) Correlation between code review process satisfaction and code quality satisfaction: I would totally agree. Tested software does not automatically mean that it is high quality (readable, maintainable). I can spot man problems in implementation which have 100% test coverage.
• (p. 11) 60% review tests: when I make a code review I rarely look at the tests, because I can tell from the implementation how testable the code is. It provides no value for me to look at the test also because I know the purpose of the implementation.
• (p. 13) Use CR for Knowledge Sharing: I don't think it is a good tool for that, since it happens after the fact, the code has already been written and that makes it harder to make bigger or fundamental changes (redo all work). Pair Programming is best to share knowledge.
• (p. 14) Benefit of Code Review: Adherence to Coding Standards/Conventions - I try not to make that part of a CR, that should be catched by automated tools and linters. I have these rules as pre-commit hooks in the projects and also as part of the CI run.
• (p. 16): "We have not enough time to do Code Reviews": it's the same as with technical debt. Code Reviews take time but reduce technical deb.
• (p. 18) Reports / Metrics: I would love to see Code Coverage from tests in Pull Requests. Also interesting would be Copy&Paste detection - I have nothing against duplicate & modify, but I discourage having exact copies of code. This can be hard to spot in larger changes.
• @shochdoerfer Yes, I have that always enabled: git config --global pull.rebase true
• @liran_tal Nice!
• @storchp @Paratron @SmartBear Well if you look at the chart, Jira seems to *be* the state of the art tool, because most people use it. I think it is a horrible tool for requirements planning because it focuses on issues and tasks (I know because I have to use Jira every day). >
• @storchp @Paratron @SmartBear A good tool for RP focuses on collaboration with all stakeholders and makes it easy especially for non-technical users to contribute to the planning, and also offers good visibility during all stages of the process. >
• @storchp @Paratron @SmartBear I wrote about how I have set it up in the past here: https://t.co/4jKk0rzQ1N
• @Bahnhofsoma @storchp @Paratron @SmartBear the other great @Atlassian tool: @trello. https://t.co/4jKk0rzQ1N
• Localisation in Germany: https://t.co/ymPKbD1ydV
• @makingthematrix I never use it, what information does it give you?
• Time to learn how to make Norwegian porridge with the Fjøsnissen: #trondheim 🇧🇻 https://t.co/8Htr9UynqP
• https://t.co/F7JnLPAItK
• @tbroyer @Maxwell_Dev True, but only one local backup is no backup in my book.
• @Paratron @Bahnhofsoma @storchp @SmartBear @Atlassian @trello It sounds like you think in a lot of Trello cards per story. There is only one story per card.
• @edimoraru @Paratron @SmartBear True, but it's also the possibilities of the tool that can limit the ways to collaborate. Jira has a bias towards expressing everything in issues, issues can only be owned (assigned) to one person,... These are decisions made by the tool, not by your process.
• @storchp @Paratron @SmartBear GitHib has projects which is awesome, too.
• @looneysquash @starbuxman Agree, but with small PRs there is usually not that much extra information anyway. Also, for how long in the future are having individual commits useful. The code is in the end what matters, not how it came to be.
• @ArashShahkar Yes, but I think it is fine to erase certain irrelevant historical data.
• @Paratron @Bahnhofsoma @storchp @SmartBear @Atlassian @trello What kind of task do you have in mind?
• @edimoraru @Paratron @SmartBear No, I will never accept that "we can just use Excel" because we will make it work.
• @looneysquash @starbuxman The history in the main branch matters, especially for keeping the release history. The example I have in the linked issue mentions baby-step commits (multiple commits to get one small feature done). Noone needs that later.
• @sag47 @looneysquash @starbuxman This has recently been addressed by GitHub with co-authored commits: https://t.co/wFc2lSRvTy
• @Paratron @Bahnhofsoma @storchp @SmartBear @Atlassian @trello That is too detailed and too job specific to keep in one tool. It should be the person who is in charge of doing it that keeps that list, in the way that suits them best. Keep in Trello what really needs to be seen by all stakeholders.
• @Paratron @Bahnhofsoma @storchp @SmartBear @Atlassian @trello Good article series is this one: https://t.co/TbkA3reIvM
• @Paratron @Bahnhofsoma @storchp @SmartBear @Atlassian @trello Progress is shown through working software/features delivered to production, everything else are bullshit metrics.
• I've completed "Chronal Calibration" - Day 1 - Advent of Code 2018 https://t.co/82FbiOfAkk #AdventOfCode
• I just completed "Inventory Management System" - Day 2 - Advent of Code 2018 https://t.co/F9RGeFRIgk #AdventOfCode
• @struberg @derekm00r3 Only if someone other than the author does the squashing. GitHub has a solution for that, too: https://t.co/wFc2lSRvTy
• @Ookami86 @INNOQ Congratulations! Have an awesome journey there!
• I got some tips @NordicTweets how to improve my workplace ergonomics and I now moved the screens further away (+15cm) and also move the table higher so it fully supports my arms. https://t.co/ffcjDbtvoJ
• @miskaknapek @NordicTweets This is actually Finland, the Kiilopää mountain. Taken @codefreeze_fi...
• @benjamin I honestly am very uncertain on what qualifies as a principle. I think this will emerge after a while once I have collected more of them.
• @benjamin Right now this repo could also be named: "Things Markus cares about so much that he writes them down so he can link others to them because he is too lazy to explain them over and over again".
• @benjamin TTS also has the ladder of leadership: where the level of freedom is very context-specific. You could look at the issues also with that model in mind.
• @benjamin Some are very broad (like Reproducible Builds = lvl 7) and some are very specific without a lot of room for interpretation (keep code left = lvl 1).
• @sag47 @looneysquash @starbuxman No, I believe not. That would be a good improvement @github.
• @atomfrede @NordicTweets Right! It's this one: https://t.co/XdDX7zskr5
• Imagine working on a 50 year old computer system: https://t.co/2D4w4lojtf
• @SmartBear Hm, I'm not on your side of the table, so my questions would focus more on the social aspect of code reviews: - what is good/bad behaviour from a reviewer - what level of detail is preferred - which tool enables collaboration on code best
• I just completed "No Matter How You Slice It" - Day 3 - Advent of Code 2018 https://t.co/U3VFhQQBc6 #AdventOfCode
• npm's 2018 JavaScript Ecosystem Survey: https://t.co/kRovIoGZ17
• @bahmutov Well deserved!
• Are we finally getting a Microsoft Browser running on Linux? https://t.co/tiDcVFmeep
• I think our tools can get better to reduce stress, but we often take them as given. >
• Issue trackers like @Jira and @github encourage issue reporters to add as many issues as they like. What if instead issue trackers would show on the "create issue" screen a linearized view of all issues, and what people are working on now?
• You could not select the priority from a list (major, minor, ...) but would be forced to rank your issue within *all* existing issues because there can only be one issue with priority 1, or 2, or 99. It's like having a kanban lane per team member.
• @saschadieter Makes it easier to test for me, since I mainly work on Linux.
• @tdpauw Is there a recording of your talk?
• @EuroTestingConf I had more than one great #ETCmoment, so I blogged about all of them here: https://t.co/wIciLZoQYf Most important was that even being in the minority as a developer I felt very included and welcome. The atmosphere was always very friendly and never hostile or too opinionated.
• @fhinkel @nodejs Ohhh, I totally forgot that we have them now, my code looks so ugly without them: https://t.co/ojaBH4Ok12
• @fhinkel @nodejs https://t.co/e5KRgYSLHj
• @xkeshav Prettier is not a linter, I'd argue.
• I just completed "Repose Record" - Day 4 - Advent of Code 2018 https://t.co/nedlliLv0A #AdventOfCode
• Cool, they can single-handedly pick one option each. What a bliss. https://t.co/9sjR7Cy2th
• @blackcat_dev *enjoy* https://t.co/co9dGQj2GJ
• Have a wonderful morning! We finally got snow here in #Trondheim. 🇧🇻 https://t.co/aUObobnTWr
• 😂🤣🤘 So true! "How to install the #Spotify Culture in Your Organization" via @jasonlittle of https://t.co/ujxgpxUvDD https://t.co/Cemsg75M05
• @lauralindal I look at you, and see you rocking this despite not getting it all laid out for you.
• @mirjam_diala Someone is reading your tweets...
• I just completed "Alchemical Reduction" - Day 5 - Advent of Code 2018 https://t.co/763m8tZaj6 #AdventOfCode
• I used a recursive approach while working with the test data. That was a bad idea once the real data came in :/
• @mirjam_diala Oh, reading Code Craft? Excellent choice, it's a fantastic book! It's a huge book, that's a solid challenge to read it in December ;-)
• @mattsches I also misread the instructions and wrote a function that is greedy deleting 2 *or more* matching characters ...
• Good Morning! #Trondheim 🇧🇻 https://t.co/cDcfn4QZ4B
• High noon in #Trondheim 🇧🇻 https://t.co/V0gpJHj954
• @mirjam_diala Uhh, nice. How did you like it?
• @AnnNat 🤞 that everything goes fine!
• If it were that easy ... https://t.co/GkR0o26MHz
• Just one more month and it is @codefreeze_fi again! https://t.co/J1mQlJFgXt #codefreeze19 #codefreeze
• I got bitten today by a nasty #JavaScript thing: const handler = async () => { try { return request(); } catch (err) { // I wanted to handle request errors here // but since request returns a promise // they won't get caught } };
• The important change to make it work is: - return request(); + return await request();
• @datenreisender Yeah, but this will only trigger if you have no awaits in the entire method.
• https://t.co/0GPXaH2TXD https://t.co/hEYx5oZGk0
• "Using 3 Random Words Is a Really Bad Idea" - because math. https://t.co/uJDmLpzgak Also because math: use 5 and you are fine. Or 1 German word (nur Spaß 😋).
• @VolkerGoebbels At one of my former companies we needed to remember very secure password because we sometimes were only able to type them in. We used sentences from German fairy tales.
• @anne_e_currie @jkriggins @tastapod @JamieDobson @emercoleman Software that is accessible for everybody and does not discriminate. Providing a useful service over profiting of user data.
• I discovered a new #firstprinciple: Make create operations succeed eventually not immediately https://t.co/N1L2BC2AKb
• And here is another #firstprinciple I discovered: Separate workflows through events https://t.co/PakeHcucbL
• In 2019: 1. Frameworks and tools don’t last in #JavaScript. Don’t hold on to your current tools too tightly. 2. #React will be the dominant framework. 3. You’ll need to learn #GraphQL. 4. Somebody on your team will bring in #TypeScript. https://t.co/aoeDS6aI8V
• @kotzendekrabbe Take a mike, go on stage. Done ;-)
• @sbley Yes.
• .@clubhouse looks like a really well thought tool for agile software delivery: https://t.co/lluniUSBx4 Thanks for sponsoring #AdventOfCode!
• We drove through the snow to #Røros Julemarked, it was not as cold as usual, this town is one of the coldest in Norway, today it was rather warm with -2°. https://t.co/pT5tTmrt86
• @kringkaste Sind ja 2-3 normale ;-)
• Miriam explains why we need @ConfBuddy: https://t.co/t72kQCgO8K
• .@OlafScholz : #CumEx - Ich will meine Steuern zurück! - Sign the petition! https://t.co/02mJRhwoRC via @Change
• #Trondheim 🇧🇻 https://t.co/XCmVU3bQSs
• New to #JavaScript? Here are inclusive and beginner friendly conferences in Europe I can recommend: @JSKongress 11+12.3.19 Munich @jsunconf 22+23.4.19 Hamburg @jsconfeu 1+2.6.19 Berlin @jscamp 18+19.7.19 Barcelona
• Now with even more correct words. 🤷‍♂️ https://t.co/sk96YR4xUT
• I wish more people would realise that prototyping #iot can be a joyful experience! https://t.co/2lzJxd5GeN
• @RidingWolf Hei! I dont know you that long! 🤙 I guess that means you *did* make new friends since then!
• @RidingWolf I guess if they keep around, while you being less and less your old self, you'll know.
• Hm ./ #adventofcode day 6 bugs me. My solution solves the example, but not the puzzle input. I tried other solutions which were accepted and they produce a result which also is not accepted, and different then mine. https://t.co/OQ7Wg0lAKo
• I think I forgot the bounding box / infinite areas.
• Yes, eliminating the infinite regions solved it. https://t.co/xXUvK4PiHt
• I just completed "Chronal Coordinates" - Day 6 - Advent of Code 2018 https://t.co/GJoGd9pBpE #AdventOfCode https://t.co/CLgYKPqU00
• @EuroTestingConf ... and in case you are a little anxious, if you want a friendly face to meet up in advance, figure out how the conference venue is situated and have a go-to buddy to hang out with all day, check out @ConfBuddy: https://t.co/bSacXR04on - we will be there!
• AWS #IoT Fleet Index can now index the connectivity status of your Things: https://t.co/2cBbz1hWW8
• I've completed Part One of "The Sum of Its Parts" - Day 7 - Advent of Code 2018 https://t.co/a5fy6DlFme #AdventOfCode
• @AnnaMelitta Was ist denn mit Pettersson und Findus?
• @benjamin you might enjoy toe https://t.co/qxYQEXw4YJ
• @emsuiko If they care about you, they will understand!
• @thecakedesk I'd love to see that. It seems that sometimes CSS gets rolled over by JSCSS just because it is very mature and established.
• @thecakedesk And with things like Parcel on the horizon many of the arguments for using JS are gone: https://t.co/ZXBw8YLIqV
• It's a good thread. https://t.co/HPyJubrTW1
• Today is a big day for us @NordicTweets! The #nrf91 #iot #lte #nbiot Development Kits are finally available for everyone and can be ordered @digikey, @mousereleceu and @FarnellNews. https://t.co/gR4uQ9yxZ8 https://t.co/VOv7jaFh4E
• https://t.co/g7gUnSMz60 $164.92 https://t.co/WJz0G8qKh4 140,78 € https://t.co/j36b6TCs0O £117.14 https://t.co/U2mrdfJs6h
• You will also get an @i_basis eSIM with the DevKit which will enable you to connect the #nRF9160 basically anywhere! 10MB traffic is included. https://t.co/2O1ruWP7Hn https://t.co/GYqkShQzIO
• Don't make me fix your bugs.
• @dtanzer @breakthesystem Sure! Thank you for this book...
• @cowglow @w3ltraumpirat @JSKongress @jsunconf @jsconfeu @jscamp @JSCraftCamp Yes, I found no date, so I did not add it. I would love to go again, it was amazing!
• @jmarcelino @NordicTweets @i_basis Yes right ... This is pretty knew tech, and countries have just started to roll out support for LTE-M and NB-IoT.
• @gfrancesco11 @i_basis The eSIM has not been standardized yet, the process was actually halted: https://t.co/6mG4U58Ccz AFAIK this SIM follows the specification and delives eSIM capabilities in a traditional SIM form factor. For more info check out iBasis site: https://t.co/vVElZdAqCE
• @liran_tal I'd love to!
• @malk_zameth Yes, I know. Bugs are inevitable and I do like to help people fix bugs. But if I am forced to do it, it makes me grumpy.
• @gfrancesco11 @i_basis Yes, as usual the standardisation effort is far behind the real world adoption...
• @malk_zameth https://t.co/MlDXH5miyQ
• This is how you build a high performance team: https://t.co/1eCeCzhzMh
• "It’s the impact that ultimately matters. NOT the intentions." And also: impact is hard to observe! Don't assume because you are not impacted, that others aren't as weel. https://t.co/htA32XWUcE
• "We’ve stopped our emulation of Spotify in Q1 of 2016 and gradually transitioned to start our own unique journey we called New World Order at the time." https://t.co/7JrJOYf5Ku
• I just completed "Memory Maneuver" - Day 8 - Advent of Code 2018 https://t.co/xR1RWc4dgP #AdventOfCode
• @kentcdodds 2. contribute them to https://t.co/Dtjd32bUw7
• I've completed Part One of "Marble Mania" - Day 9 - Advent of Code 2018 https://t.co/59Qp8HWKaT #AdventOfCode (part 2 is still calculating ...)
• @datenreisender Too long. I need to change the datastructure.
• @datenreisender I did complete part 1 😉!
• @datenreisender It's what I said in the tweet above. And to be fair, the manager in this example did not define their expectations well.
• I hope @BurgerKing and @McDonaldsCorp are paying attention. Superior taste and eco friendliness is not a contradiction! https://t.co/eVNOLIm2V7
• @RidingWolf Amazon?
• @RidingWolf If you select "Prime" it will limit the result only to stuff shipped from their warehouse.
• @RidingWolf Yeah, but it will be shipped in one package at least.
• @Lynoure It's interesting to learn how they make money: https://t.co/ZPn9JhJHM9
• Yes, it's that cold in Norway. 🇧🇻 Trondheim has -15, Røros -38. https://t.co/Wv0Ul6lu4p
• We need to thank @sarahmei more for the countless times she has shown us an image of our profession that we neglect to see. https://t.co/RQsO7Oi3lz
• I just completed "Marble Mania" - Day 9 - Advent of Code 2018 https://t.co/59Qp8HWKaT #AdventOfCode - a linked list was needed: https://t.co/b2Hdtb6q7U
• #Sunset over #Trondheim 🇧🇻 https://t.co/po4LJy2Lr9
• I see very few engineers express the environment they would love to work in. With so few data points available companies will keep focusing on the easy things: making the time around the job fun, instead of making the job fun. https://t.co/KlWUUEbadR
• A while ago I wrote about what specific conditions (or perks) are worth to me: https://t.co/qYjLF88cqK Which means that offering them instead of Foosball tables and fruit baskets translate directly into spending less for salaries.
• @VolkerGoebbels You could put it the other way around. If these things I list are not available I will need a higher salary to work for that company. I have worked for startups in the past with a salary I would never work for at body-leasers like Accenture.
• I just completed "The Stars Align" - Day 10 - Advent of Code 2018 https://t.co/Yv9irArrYT #AdventOfCode
• I just completed "Chronal Charge" - Day 11 - Advent of Code 2018 https://t.co/DiTxgYwNJ5 #AdventOfCode
• @calibanatspace https://t.co/S4bgPNDmuI
• I've completed Part One of "Subterranean Sustainability" - Day 12 - Advent of Code 2018 https://t.co/wewN9mVTe4 #AdventOfCode
• Part 2 is still nagging me... https://t.co/57jlULoF7x
• @calibanatspace @retokiefer WO SIND DIE GELBEN SCHUHE?! https://t.co/euAnw5fCiU
• @marudor SVG: https://t.co/zCZxgY87KZ https://t.co/mvFP1G3Nj4
• Anyone of my trusted followers can recommend this conference? https://t.co/RA1vdycvjv
• I just completed "Subterranean Sustainability" - Day 12 - Advent of Code 2018 https://t.co/wewN9mVTe4 #AdventOfCode (after fixing a off-by-one-error)
• "Mine Cart Madness" - Day 13 - Advent of Code 2018 https://t.co/xEQzLYx0rI #AdventOfCode - I have a solution, looks right visually, but it's not accepted: https://t.co/Qd9QG3kIsI
• @dtanzer Looking forward to seeing the results!
• "Which engineer puts spaces in their folder?!" Me: https://t.co/im5qqGHBNf
• Visual debugging shows the bug ;-) The carts are not turning... https://t.co/0Efe7SlZxR
• So, I've completed Part One of "Mine Cart Madness" - Day 13 - Advent of Code 2018, but part 2 is still calculating (at ~0.5ms per tick). I wonder if there is also a different approach to the solution.
• Want to work on one of most exciting fields in #fintech: creating cashless societies? Check out @signicat which are based here in #Trondheim, they are behind the most widely used digital identity platform in the Nordics. Check out their job listings at https://t.co/zZGXlqx1Hu
• I've completed Part One of "Chocolate Charts" - Day 14 - Advent of Code 2018 https://t.co/ZFlbq0oKrq #AdventOfCode
• Today we celebrate the successful launch of the long-range wireless #nrf9 series @NordicTweets in all offices with a special cake: https://t.co/J26snUf5rw
• Oh, @twitter can now hyphenate: https://t.co/OZalJxB9y1
• @iHarshadEC @NordicTweets The #nrf91 SIP is kinda white, so that fits well: https://t.co/PAZUtVwFkL
• I just completed "Chronal Classification" - Day 16 - Advent of Code 2018 https://t.co/367gCeGT3T #AdventOfCode
• Thanks for the invite to the #7covers #bookchallenge @datenreisender and @Lynoure. I will be posting the covers of 7 books I love: no explanations, no reviews. And because I am an engineer, let's start with book 0: https://t.co/atw2wLiMA3
• Hello from #Trondheim 🇧🇻 https://t.co/rYLC8ECggV
• @lsmith You should come to @SoCraTes_Conf ... we have that.
• This was taken at 14:09 today ...
• Certified box checker. https://t.co/tFyhEBNr5w
• Out of Control Kevin Kelly 1994 https://t.co/FzkfTd6xL5 https://t.co/fLgYqMX6No
• I am 38 and until now I was not able to use Nivea. Thank you @Beiersdorf_AG for this gender bullshit. https://t.co/jAelzlfVfG
• @lux_lock @Beiersdorf_AG @evenprimeandco From my personal experience of using skin care products: this is not a question of gender but much more complex. It annoys me that there needs to be everything for the two most common sexes, because it's easy to market.
• Satisfaction > Happiness https://t.co/RaWEcV2umG
• Masters of Doom David Kushner 2003 https://t.co/nsrc6RQ3qZ
• @AnnNat https://t.co/Ub3f5But0w
• @AnnNat I have hugs for you!
• @Maggysche OMG. Epic present.
• @jacek_smolak @lux_lock @Beiersdorf_AG @evenprimeandco It's not only men that shave. It would be better and more inclusive to make a "Nivea: for shaved skin".
• @EmmaWedekind Thank you that you put up with this shit and keep presenting a different view on how an engineer looks like. 🙏💪
• @EmmaWedekind It's your job, but with some extra challenges I do not face as a white man. I appreciate this because I know from talking to female engineers how this can wear down the joy in our line of work.
• Antifragile Nassim Taleb 2012 https://t.co/U4qrchdIrZ
• "Do You Need a Degree?" No. "Is Computer Science important?" Yes. https://t.co/5Tktj8NqbB
• I've just discovered, that @socracan has announced the 2019 dates: April 25-28th, 2019
• Change that is managed means it's forced and not understood. Only change that emerges prevails. https://t.co/7NTdfKKFvE
• Currently working on my talk about testing cloud-native systems, which will premiere @EuroTestingConf in Valencia! There are still tickets available, and I promise you that this conference is something you do not want to miss! https://t.co/zyjpYHlK1E https://t.co/N4mkhbfndx
• Toller Lightning Talk von @mirjam_diala zum Wieso und Wie des #testing im #Frontend: https://t.co/IBwjdHqp72 Die Beispiele sind leicht verstaendlich und zeigen: Testen is' kein Hexenwerk .... und es lohnt sich!
• @liran_tal @EuroTestingConf @goldbergyoni Thanks, I'm really looking forward to share this talk and see how others are approaching this.
• @MaritvanDijk77 https://t.co/vMH02DaxAX
• They say, when making a sculpture, you only need to cut that away from the block that's not part of the sculpture. When preparing a talk, you first build a solid block with a thousand great ideas. And then you need to cut away your own ideas down to a few. THAT really hurts.
• @liran_tal @EuroTestingConf @goldbergyoni That comment made me add a slide! Although I focus on e2e tests in this talk I still have tons of unit tests. e2e tests will only cover the happy path and possible inputs are limited. Unit tests are super valuable, because they are fast and located close to the implementation.
• 65 slides and counting ./ https://t.co/lxMqvy0MP3
• @NativeWired Yes, I also thought that this could be a good ebook. Will try this out, because it has a lot of code examples which won't make it into the talk.
• @YvesHanoulle True. I usually do well with <1 slide / minute. This is a 30 min talk...
• @e_p82 @davidpich It's good that I will give this talk multiple times, so I can change the emphasis depending on the audience. I can put the focal point on code for the JavaScript folks, infrastructure details for DevOps people, and approach/workflow for the testers.
• Creativity, Inc. Ed Catmull 2014 https://t.co/HKJ4zfts0V
• @RidingWolf https://t.co/NhRyIhFrnO
• @socracan any recommendations for good hotels around the venue? Or is the conference hotel also a good option?
• @socracan Woha, cool. I have never been to a SoCraCan, and I have so many questions ;-)
• @MIndfulTester @melthetester Interesting idea to use a mind map to drive a presentation and navigate to the slide(s) depending on the audience!
• @Ravetracer Twitter bietet ein viel höheres Maß an Interaktivität mit den Followers, und es entwickeln sich sehr schnell Diskussion weil auch andere schnell darauf aufmerksam werden (weil man sieht wenn ein Followee einem Account antwortet, dem man auch folgt).
• @Ravetracer Blogs sind sehr viel statischer geworden. Threads in Twitter lassen sich auch viel bequemer erstellen, man fängt mit kleinen Teilen an, für einen Blog erwartet man schon eher eine in sich geschlossene Abhandlung.
• @Ravetracer Twitter hat das im UI auf der Website und in der App bereits. Beim erstellen kann man mit ➕ weitere Tweets zu einem Thread hinzufügen und alle auf einmal absenden. Praktisch sind Threads nur Antworten auf einen vorigen Tweet.
• This and the details about the process in https://t.co/ZXHphtJ8NE really give a good idea why this price works so well, especially for candidates: you get the opportunity to really show the way you think and approach new problems, which is in the end what we hire engineers for! https://t.co/eLjsr0uEd4
• In case you need a motivator for 2019 to apply as a speaker to conferences, let me tell you this: If you care about a topic, you *should* talk about it, not matter if you consider yourself an expert, or not! https://t.co/XQezKB7CBq