Artistry of Code

Another episode released! In #005 we’ve tried to answer the question “Who is the QA anyway?” of delivered software. Is it a manual tester, Quality Assurance Engineer, or someone else?

We’ve analyzed the typical process of Agile software development to find an answer. Do you have your opinion already? Press the “play” button and compare it to our findings!

In the third episode of the Snippet series, Grzegorz shares his tips on implementing the "Learn, Apply, Repeat" mantra. If you were looking for ways on how to structure your personal development - you will find this episode really useful!

The full article can be found here:
https://www.linkedin.com/pulse/learn-apply-repeat-grzegorz-godlewski

Make sure you've subscribed to our podcast, don't hesitate to share this episode with others and tell us what you think about the content we deliver.

Episode #004 is already here! This time we wanted to share with you the selection of tools that might help you forget about the routine tasks and focus on things that really matter (and fortunately machines can’t do them yet 😅 ) - solving business problems.

We’ve brought our daily helping tools that can: 

• keep an eye on the code quality and style, help you write the code or can be useful when testing or deploying it;
• collaborate with other developers;
• visualize the problem to solve and the solution from a higher perspective.

We encourage you to try out our selection of tools and we’re looking forward to your proposals that you consider handy in the daily work.
 
List of contents:
00:00 🎼 Intro
00:47 💡 What NodeJS tools Marek found lately?
02:52 😓 What occupied Artur that much?
04:37 📚 What Grzegorz is preparing to?
05:37 🏅 What tools can help us deliver the code of good quality?
22:04 🤝 How proper tools can help us with collaboration?
38:50 🔎 What tools can be handy in the testing procedure?
48:54 🤖 What can assist us in our daily work?
55:20 💌 Will you share your favourite toolkit with us?

Tools mentioned in the episode:

General usage:
➭ SonarQube: https://www.sonarqube.org/
➭ JetBrains IDEs: https://www.jetbrains.com/products/
➭ JetBrain Code With Me: https://www.jetbrains.com/code-with-me/
➭ docker-compose: https://docs.docker.com/compose/

Visualization:
➭ Excalidraw: https://excalidraw.com/
➭ Miro: https://miro.com/
➭ Figma: https://www.figma.com/
➭ Web Sequence Diagrams: https://www.websequencediagrams.com/
➭ Obsidian: https://obsidian.md/
➭ mermaid.js: https://mermaid-js.github.io/mermaid/#/ 

For Node:
➭ eslint: https://eslint.org/
➭ prettier: https://prettier.io/
➭ jest: https://github.com/facebook/jest
➭ npm-check: https://github.com/dylang/npm-check
➭ stryker: https://github.com/stryker-mutator/stryker-js

For PHP:
➭ humbug: https://github.com/humbug/humbug
➭ PHP CodeSniffer: https://github.com/squizlabs/PHP_CodeSniffer

For testing:
➭ MockServer: https://mock-server.com/
➭ Gatling: https://gatling.io/
➭ ToxiProxy: https://github.com/Shopify/toxiproxy
➭ Blockade: https://blockade.readthedocs.io/en/latest/ (deprecated)

In the second episode of The Snippet Series Artur is giving his insights into the topic of proper sizing "unit" for Unit Testing.

• How to make Unit Testing well-grained? 
• Is every piece of code worth having separate test suite? 
• What to do when the size of your test files overwhelm you? 

You can find answers to those questions in the episode.

00:00 Intro 🎼
00:28 How it all started? 📆
01:22 How to classify Unit Testing? 👨🏻‍🏫
02:07 What is the "unit" for Unit Testing? 🧩
03:41 Is every "unit" worth being tested? 🔮
06:15 What if the "unit" is too big? 🐋
07:42 Summary 🗒

Make sure you've subscribed to our podcast, don't hesitate to share this episode with others and tell us what you think about the content we deliver.

In the third episode, Artur, Marek and Grzegorz share their approach towards refactoring of code.

• How to be well prepared?
• What to focus on?
• What to avoid while performing refactoring?

Answers to these and other questions can be found inside.

Make sure you subscribe to the show in your podcasting app! You can also drop us a review :)

In the first episode of our SNIPPETS series, which we deliver to you with a promise of all episodes being not longer than 10 minutes, Marek talks about migrating the code to TypeScript, the ways to do that right and safe, but also explaining why it is a business decision, not only a technical one.

In this episode you will hear about:
🎼  00:00 Intro and series introduction
👉  00:30 TypeScript was not great at the beginning
👉  01:27 Personal disclaimer about Marek and TypeScript
👉  02:00 TypeScript and business :moneybag:
👉  02:30 How to justify the cost of the migration?
👉  03:03 Why it’s worth to await a promise? 🔐
👉  04:30 What are the not obvious benefits of having types in your code?
👉 05:35 How did the AirBnb benefit from implementing TypeScript in their organisation? 🛏
👉  05:57 Big picture tips and tricks on coding part of this process 💻
👉  08:12 Sad information about TS and quality of the code 😭
👉  08:29 Outro 👋

How do you find the SNIPPETS series? We would like to hear your feedback!
Tell us what you think, so that we can prepare more interesting content for you to enjoy.
Hear you next time!

Links mentioned in the episode:
https://twitter.com/remohjansen/status/1093815648566894594
https://marekurbanowicz.medium.com/migrating-large-codebase-to-typescript-do-it-right-from-the-beginning-7109a80b2a3d

Visit us on:
- Facebook: https://www.facebook.com/ArtistryOfCode
- Twitter: https://twitter.com/ArtistryOfCode
#typescript #javascript #nodejs #SoftwareDevelopment #SoftwareEngineering #programming #software

In episode #002 we’ve brought up the topic that some love, others hate, but all of us need to take care of eventually. Errors, defects, mistakes, bugs... It’s all about them, or rather how to get rid of them and make it stay this way.

In this episode you will hear about:

👉  00:00 Intro 🎼
👉  00:30 How grateful we are for your feedback and attention 🤗🥰
👉  01:20 What makes Artur excited about his new job? 🥚
👉  04:35 How effectively Marek is performing full text search? 🕵️‍♂️
👉  06:50 News from Grzegorz and comments on a recent disaster in OpenSource 🧐
👉  10:56 What’s a bug anyway? 🐛 
👉  12:35 Where do bugs come from? 🗑🕳
👉  22:35 What does it mean to fix the bug? 👨‍🔧
👉  34:08 If fixing bugs can be fun? 🥳
👉  36:13 How to get the most out of the buggy situation? 😎
👉  40:04 What to do and what to avoid to keep their number under control? 👮‍♀️
👉  49:19 How precious is your feedback? 💰

We would like to hear your feedback! Tell us what you think, so that we can prepare more interesting content for you to enjoy. Hear you next time!

Links mentioned in the episode:

• https://oss.redis.com/redisearch/
• https://snyk.io/blog/open-source-npm-packages-colors-faker/

Visit us on:

• Facebook: https://www.facebook.com/ArtistryOfCode
• Twitter: https://twitter.com/ArtistryOfCode

#bugs #bug #debugging #qos #QualityOfSoftware #SoftwareDevelopment #SoftwareEngineering #programming #software #defects #opportunities

Who we are, what we do, where we are from.

In the first episode: Artur, Marek and Grzegorz talk about:

- measuring the value of software delivery,
- "managing the time" or rather, "managing ourselves in time",
- handling our egos at work,
- introducing "Programmers Workout" to the weekly plan.

We would like to hear your feedback! Tell us what you think, so that we can prepare more interesting content for you to enjoy. Hear you next time!

Visit us on:
- Facebook: https://www.facebook.com/ArtistryOfCode
- Twitter: https://twitter.com/ArtistryOfCode

#NewYearResolutions #future #development #SofwareDevelopment #SoftwareEngineering