Podcast
Technology Radar Review
Hosted by Grzegorz Duda · POLISH
Bądź na bieżąco z trendami w IT.
Dołącz do Grupy Architektów, którzy przeanalizują ThoughtWorks Technology Radar vol. 23 uzupełniając go o swoje przemyślenia bazujące na wieloletnim doświadczeniu.
Więcej na https://dworld.pl/technology-radar/
4episodes
Episodes
Newest firstAll episodes
#004: Co powinien wiedzieć Architekt
Feb 25, 202101:54:42Tap to summarizeWięcej na https://dworld.pl/technology-radar/ Dowiedz się co powinien wiedzieć Architekt i jak się przygotować do takiej roli. Swoim doświadczeniem podzielą się Jakub Kubryński, Jakub Pilimon, Sławek Sobótka i Grzegorz Duda.
Transcribe →#003: The Next Big Thing in IT in 2021
Feb 25, 202101:54:23Tap to summarizeWięcej na https://dworld.pl/technology-radar/ Jakub Nabrdalik, Tomasz Nurkiewicz, Jarek Pałka, Sławek Sobótka, Mariusz Gil i Grzegorz Duda rozmawiają na temat tego co było znaczące w IT w 2020 i co będzie w 2021.
Transcribe →#002: Use “remote native” processes and approaches
Dec 31, 202000:49:37Tap to summarizeWięcej na https://dworld.pl/technology-radar/ Jakub Nabrdalik, Tomasz Nurkiewicz i Andrzej Krzywda rozmawiają na temat ThoughtWorks Technology Radar vol.23. Use “remote native” processes and approaches (trial) As the pandemic stretches on it seems that highly distributed teams will be the “new normal,” at least for the time being. Over the past six months we’ve learnt a lot about effective remote working. On the positive side, good visual work-management and collaboration tools have made it easier than ever to collaborate remotely with colleagues. Developers, for example, can count on Visual Studio Live Share and GitHub Codespaces to facilitate teamwork and increase productivity. The biggest downside to remote work might be burnout: far too many people are scheduled for back-to-back video calls all day long, and this has begun to take its toll. While online visual tools make it easier to collaborate, it’s also possible to build complex giant diagrams that end up being very hard to use, and the security aspects of tool proliferation also need to be carefully managed. Our advice is to remember to take a step back, talk to your teams, evaluate what’s working and what’s not and change processes and tools as needed. Linki do stron i narzędzi: https://soundofcolleagues.com/ https://www.noisli.com/
Transcribe →#001: Diagrams as code (Trial)
Dec 30, 202000:36:03Tap to summarizeWięcej na https://dworld.pl/technology-radar/ Jakub Nabrdalik, Tomasz Nurkiewicz, Andrzej Krzywda i Grzegorz Duda rozmawiają na temat ThoughtWorks Technology Radar vol.23. Diagram as code (trial) We’re seeing more and more tools that enable you to create software architecture and other diagrams as code. There are benefits to using these tools over the heavier alternatives, including easy version control and the ability to generate the DSLs from many sources. Tools in this space that we like include Diagrams, Structurizr DSL, AsciiDoctor Diagram and stables such as WebSequenceDiagrams, PlantUML and the venerable Graphviz. It’s also fairly simple to generate your own SVG these days, so don’t rule out quickly writing your own tool either. One of our authors wrote a small Ruby script to quickly create SVGs, for example. Linki do stron i narzędzi: https://graphviz.org/ https://structurizr.com/ https://yuml.me/ https://www.websequencediagrams.com/ https://miro.com/ https://www.eclemma.org/jacoco/ https://www.markdownguide.org/cheat-sheet/ https://asciidoc.org/ https://c4model.com/ https://sequencediagram.org/ https://structurizr.com/dsl https://huion.com.pl/ https://github.com/Netflix/vizceral https://www.skylight.io https://github.com/Adaptech/les https://pandoc.org/
Transcribe →