Zachęcam do oglądnięcia mojego Lightning Talka pod tytułem "Nic nie wiem". Opowiedziałem jak moje doświadczenie w projektach pokazało, że warto mniej wiedzieć i zakładać a więcej pytać i starać się zrozumieć czego chce od nas klient.

A few weeks ago,  on my way to the .NET Developer Days conference, I had a thought that I must be getting old. That’s because the only book I took with myself was about parenting 🙂 Before, usually, it was something really technical that I don’t have time for and somehow I plan to catch up on the train or in the hotel. I had an interesting conclusion for the first time in my life, that actually putting the hard work to become a better parent, all the lessons learned through the period of raisin...

I have met and talked to a lot of developers in my life. I went through the whole lifecycle of software production many times. People have changed, but the projects that have been implemented, are happily still running in production (at least most of them, let’s say :)). What I have noticed during this period of over 10 years working with the software and people producing it, is that many developers have quite a strange approach to work. In IT there’s this request type called “Fire and forget”, ...

Once a while, recruiters from the company I work at, ask me whether I have some friend (developer) who’s looking for a job. Typically, this kind of dialogue looks something like: Recruiter: „Hey Darek! I have a great job offer for a .NET developer! Maybe you’ve got someone who would be interested?” Me: „Show me what you got. Yeah… I have one who knows all the technologies and worked with this kind of architecture. Although he’s got half a year less experience than r...

It’s a good practice to make all things done at the first approach. But in the real world it’s ot always possible - for example we need to ask customer for clarification and it will take some time, or worst - we don’t have enough time right now to implement things in the right way. In order to adress this issue, a TODO was invented to mark all those places in code requiring additional work. But the main disadvantage of TODO is that we mark code with it, commit it and forget about it. Sometimes somebody a...

Sławek Techniki programowania / Wzorce operacyjne / Wzorce projektowe Teraz omówię wzorzec Iterator(Iterator), jak sama nazwa wskazuje służy do iterowania po kolekcjach, obiektach itp. To tak w dużym skrócie, dokładniej jest opisany w artykule. CelZapewnienie sekwencyjnego dostępu do obiektu lub obiektów składających się z określonej liczby elementów bez ujawniania reprezentacji wewnętrznej tych obiektów.

Is Artificial Intelligence going to replace us? I’ve had yesterday a short discussion about replacing programmers by any kind of Artificial Intelligence. That brought me some conclusions linked to the problems I always had to solve being a manager. What I want to focus on is neither to question if the software will replace programmers writing software nor when w...

2 miliardy pozycji dziennie. Jak przetworzyć taką liczbę i nie zapłacić masy dolarów? Zapraszam do drugiego artykułu z serii.

Podstawowe informacje o message broker i rabbitmq z uzyciem easynetq jako klienta.

I’ll describe a few patterns that enabled me to process 2 billions items per day using Azure Functions. Yes 2 billions items per day. The aim of this trial was not to check whether you can do it with Azure Functions. You can do it easily. The goal was to do it in a cost-aware and cost-wise manner, enabling fast processing with a small amount of money spent on this.