Cecilie 🧙♀️
@cvennevikSoftware dev 🇳🇴🏳️⚧️ | I get overexcited about coding | she/her | @[email protected]
Similar User
@kode24no
@pbourgau
@Heimeshoff
@einarwh
@ncraftsConf
@Software_Capts
@KellyJille86
@tpierrain
@ygrenzinger
@trondhjort
@hsulriksen
Reminder that I'm still active on the Fediverse at hachyderm.io/@cvennevik, but also: If another social media platform isn't your style but you use an RSS reader, I've also started blogging! So far, this one is probably most relevant to my circle: cvennevik.no/post/code-revi…
I wonder when Twitter gets around to reading my bio and suspending me lol Anyway, hope to see you all elsewhere!
- Magien med mob-testing er at dere lærer mye og blir mer kreative. I tillegg er det tidsbesparende! Dere vil jobbe bedre sammen over tid og det vil gjøre alle til bedre testere, skriver Lena i @kantega 💪 kode24.no/artikkel/lena-…
The core idea is simple, but almost never admitted: if, in a society of people who mostly follow certain rules and conventions, you systematically re-train yourself to ignore some of those conventions, you suddenly feel like a superhero who "sees the matrix".
Whatever the opposite of “hardcore” 10x rock star dev is, that’s what I want. cosycore, moving slowly, making things right, petting the dog, naps, staring out of the window pondering problems and drinking tea.
5-Minute DevOps: Pain-Driven Development by @BryanFinster riseandfallofdevops.com/5-minute-devop… #developers #DevOps
We have updated the #MobProgramming book, and changed its name. I now call it "Software Teaming" (based on the idea from @AmyCEdmondson's book "Teaming") Here is a link to the new edition of the #SoftwareTeaming book available in Kindle or Paperback: amazon.com/dp/B0BLG1QTYK
I would like to stress “DO write the documentation that is helpful” instead of saying “keep to minimum”. You know. That README, that piece of javadoc, that clarifying example. We know how nice they are to come across. Be the dev who writes them.
Don’t wait for a feedback loop to kick in to deal with a problem. Flag a problem in the team before the retro. Remove a dependency before the team review. Change the plan before the daily sync. Don’t wait to adapt.
There is a huge gulf between the software delivery approaches (SAFe, LeSS, etc.) that fundamentally assume that a "machine" ⚙️ is needed versus those approaches (@TeamTopologies, original agile, etc. ) that assume that the nurturing of an ecosystem 🌱 is needed. 1/
United States Trends
- 1. #SmackDown 44,7 B posts
- 2. Jared McCain 10,8 B posts
- 3. Khalid 24,6 B posts
- 4. Kendrick 824 B posts
- 5. Bayley 4.252 posts
- 6. #OPLive 1.836 posts
- 7. Bianca 17 B posts
- 8. Chaz Lanier N/A
- 9. MSNBC 275 B posts
- 10. #loveafterlockup 1.709 posts
- 11. #AskShadow 32 B posts
- 12. Kevin Owens 3.146 posts
- 13. Chelsea 51,3 B posts
- 14. Creighton 2.868 posts
- 15. Scott Bessent 24,2 B posts
- 16. Ben Simmons 2.876 posts
- 17. Shinsuke 2.105 posts
- 18. Cam Johnson 1.930 posts
- 19. #OPNation 1.070 posts
- 20. Jade Cargill 3.803 posts
Who to follow
-
𝙠𝙤𝙙𝙚24
@kode24no -
Philippe Bourgau
@pbourgau -
Marco Heimeshoff @[email protected]
@Heimeshoff -
Einar W. Høst
@einarwh -
NewCrafts
@ncraftsConf -
SoftwareCaptains
@Software_Capts -
Kelly Jille 🇺🇦
@KellyJille86 -
use case driven
@tpierrain -
Yannick Grenzinger
@ygrenzinger -
Trond Hjorteland
@trondhjort -
Harald S. Ulriksen
@hsulriksen
Something went wrong.
Something went wrong.