Log in

goodpods headphones icon

To access all our features

Open the Goodpods app
Close icon
headphones
Around IT in 256 seconds

Around IT in 256 seconds

Tomasz Nurkiewicz

Podcast for developers, testers, SREs... and their managers. I explain complex and convoluted technologies in a clear way, avoiding buzzwords and hype. Never longer than 4 minutes and 16 seconds. Because software development does not require hours of lectures, dev advocates' slide decks and hand waving. For those of you, who want to combat FOMO, while brushing your teeth. 256 seconds is plenty of time. If I can't explain something within this time frame, it's either too complex, or I don't understand it myself. By Tomasz Nurkiewicz. Java Champion, CTO, trainer, O'Reilly author, blogger
bookmark
Share icon

All episodes

Best episodes

Top 10 Around IT in 256 seconds Episodes

Goodpods has curated a list of the 10 best Around IT in 256 seconds episodes, ranked by the number of listens and likes each episode have garnered from our listeners. If you are listening to Around IT in 256 seconds for the first time, there's no better place to start than with one of these standout episodes. If you are a fan of the show, vote for your favorite Around IT in 256 seconds episode by adding your comments to the episode page.

Around IT in 256 seconds - #59: How compilers work: from source to execution
play

11/29/21 • 4 min

A compiler is an application that turns text into an executable program. It’s quite extraordinary how much work these complex pieces of software are doing. Pretty much every compiler works by executing several phases. Each phase takes the input of the previous ones to finally produce the runnable code. Let’s take a journey through the compiler internals.

Read more: https://nurkiewicz.com/59

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode
Around IT in 256 seconds - #9: Retrying failures

#9: Retrying failures

Around IT in 256 seconds

play

07/21/20 • 4 min

I find it quite fascinating how many failures in complex systems could be avoided if we simply... tried again. So how so you retry effectively, so that your systems are much more fault-tolerant and less brittle?

Read more: https://256.nurkiewicz.com/9

Get new episode straight to your mailbox: https://256.nurkiewicz.com/newsletter

bookmark
plus icon
share episode

DRY, or don’t repeat yourself is a common principle in pSpring AOP riddlerogramming. That’s why we invented functions and objects. But some sources of duplication are really hard to get rid of. Well, sometimes it’s even hard to realize there’s duplication in the first place! Common examples are logging, validation, checking security, starting a transaction. Often, these are one-liners that are too simple to extract. Too mundane too bother. And too ubiquitous to forget.

Read more: https://nurkiewicz.com/66

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode

Functional programming means programming using functions. See, I need much less than 256 seconds for that! Unfortunately, this definition is as useful as saying that object-oriented programming means programming with objects. So let’s dive deeper. First of all, I mean pure functions as defined by mathematicians. In math, a function always returns the same output for a given input. A length of a string is a function. A form validator is typically a function as well. For the same form inputs it always returns the same result: valid or invalid. On the other hand, returning the current date for a given location is not a function. Or reading a file.

Read more: https://nurkiewicz.com/49

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode
Around IT in 256 seconds - #48: Distributed tracing: find bottlenecks in complex systems
play

09/07/21 • 4 min

Life used to be simple. In a traditional monolithic application, when a failure occurred, you could easily find the problem. When an exception bubbles up, it appears throughout all stack frames. You can easily examine which methods or functions were invoked from each other. You can see application layers involved. Moreover, it’s fairly easy to profile performance bottlenecks. Answering these questions becomes much harder when there are multiple systems involved.

Read more: https://nurkiewicz.com/48

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode
Around IT in 256 seconds - #65: Zero Downtime deployment: If it hurts, do it more often
play

01/10/22 • 4 min

Remember the days when deploying a new version of your application required downtime? If your application is particularly important, you might have had to schedule a maintenance window. Or perform the deployment in the middle of the night to avoid disruption. Today’s tools and DevOps practices allow deploying tens or even hundreds of times per day. With no downtime, and no noticeable disruption. Sometimes every commit is deployed automatically to production within minutes. How’s all this possible?

Read more: https://nurkiewicz.com/65

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode

Ethereum is a network of computers with no central trusted authority. They achieve consensus by running computation-intensive algorithm, known as proof-of-work. The agreed state is added to an append only ledger, known as blockchain. Yes, Ethereum is yet another blockchain. And it’s used to track transactions in a cryptocurrency, known as Ether. However, unlike Bitcoin, it’s much more than a simple log. Bitcoin accounts simply hold currency. Ethereum accounts can run programs as well. Ethereum network is actually one, huge computer!

Read more: https://nurkiewicz.com/80

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode
Around IT in 256 seconds - #68: ACID transactions: don't corrupt your data
play

02/01/22 • 4 min

Transactions in SQL databases are rock-solid. By reading and modifying data within a transaction we limit the risk of data corruption. Actually, there’s an acronym describing transactions: ACID. Which stands for: atomicity, consistency, isolation and durability. A good database engine follows these properties religiously. NoSQL engines, on the other hand, trade ACID properties for availability or speed. Of course, this is a gross simplification. Anyways, NoSQL crowd coined another acronym: BASE. Which stands for: basically available, soft state and eventually consistent. We’ll leave BASE for another episode.

Read more: https://nurkiewicz.com/68

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode

Version control systems, like git, serve two purposes. First of all, they allow collaborating on the same code by multiple developers. Collaboration is needed for any non-trivial project. Secondly, they keep the history of changes. Modification history allows tracking bug fixes and regressions. That, and many other applications of version control, will become obvious in a second.

Read more: https://nurkiewicz.com/67

Get the new episode straight to your mailbox: https://nurkiewicz.com/newsletter

bookmark
plus icon
share episode
Around IT in 256 seconds - #1: Circuit Breaker

#1: Circuit Breaker

Around IT in 256 seconds

play

05/12/20 • 4 min

Circuit breaker is a design pattern that prevents cascading failures in distributed systems. More details: https://microservices.io/patterns/reliability/circuit-breaker.html and https://docs.microsoft.com/en-us/azure/architecture/patterns/circuit-breaker.

Circuit breaker implementations:

https://github.com/resilience4j/resilience4j (Java)

http://www.thepollyproject.org/ (.NET)

https://github.com/rubyist/circuitbreaker (Go)

https://doc.akka.io/docs/akka/current/common/circuitbreaker.html (Scala/Akka)

https://github.com/yammer/circuit-breaker-js (JavaScript)

This episode was originally twice as long. If you wish to hear full, director's cut version, check out my mailing list: https://256.nurkiewicz.com/newsletter. I will also notify you about new episodes and add some extra content.

Suggest your topics: https://github.com/nurkiewicz/256/issues/new/choose

bookmark
plus icon
share episode

Show more best episodes

Toggle view more icon

FAQ

How many episodes does Around IT in 256 seconds have?

Around IT in 256 seconds currently has 98 episodes available.

What topics does Around IT in 256 seconds cover?

The podcast is about Podcasts and Technology.

What is the most popular episode on Around IT in 256 seconds?

The episode title '#96: Border Gateway Protocol: the duct tape that makes the Internet work' is the most popular.

What is the average episode length on Around IT in 256 seconds?

The average episode length on Around IT in 256 seconds is 4 minutes.

How often are episodes of Around IT in 256 seconds released?

Episodes of Around IT in 256 seconds are typically released every 7 days, 1 hour.

When was the first episode of Around IT in 256 seconds?

The first episode of Around IT in 256 seconds was released on Apr 27, 2020.

Show more FAQ

Toggle view more icon

Comments