Michał Jasiorowski

I don't know if this is only my observation or if someone else feels the same. One of the biggest problems with infrastructure is that it is too often isolated from the development teams. Companies often extract a separate team responsible for the infrastructure at some point. As this team grows, it is then split into multiple others. These teams handle topics like identity access management, orchestrators, API gateways, or build pipelines. This, in turn, leads developers to worry less and less about infrastructure. It is not uncommon for software architects to treat infrastructure-related topics as a second category. There are DevOps; we can put it on their shoulders. This is an anti-pattern. There are so many things that can go wrong: - Database, storage, and cache - API gateway and load balancers - IAM - Orchestrators, message brokers - Security of infrastructural components And many more. At some point, I decided to start collecting topics related to architecture that are most important from the software architect's perspective. The result? I will give a talk about it at the Devoxx conference in June :) Feel free to check the details here: https://lnkd.in/dmXia-Qp Who do I see there? :) #softwarearchitecture #devops #softwaredevelopment

13

6 komentarzy

Quick engineering salary comparison based on the #DEVBG stats from 2023 and 2024 in the Bulgarian IT industry. Dev.bg publish yearly a summary of the Bulgarian IT engineering salaries based on the job openings offers on their platform. https://lnkd.in/dNU5MD8D (2023 stats) https://lnkd.in/dX_dxvP7 (2024 stats) Based on the population data (let's assume it's a proper representation of the real world) we can determine the following: 1. PHP should be dead but it isn't (unfortunately) as it's one of the two categories with growing salaries in all job positions and ranges. 2. The second is the full stack development with a minimum drop of 65 levas in the first MID range(2-5 years) 3. All ranges except the Senior level(5+ years of experience) have a drop in salary compared to 2023 but for some seem negligible compared to the notion in the industry that "it's going down and AI will take over the world" :) 4. We can see that seniority still counts and there is now a shift towards growth of salaries of more senior people compared to others as the market tries to regulate. 5. There is still a lot of green for a "dying" and "shrinking" industry. P.S To anyone interested I can share the excel if needed but it's quite straightforward to generate it. *Legend: Diff min Mid - difference in the minimum ranges for a category between 2023 and 2024 Diff max Mid - difference in the maximum ranges for a category between 2023 and 2024 Diff min Sen - difference in the minimum ranges for a category between 2023 and 2024 Diff max Sen - difference in the maximum ranges for a category between 2023 and 2024 Diff min Sen Median - difference in the minimum ranges based on the provided median from dev.bg for a category between 2023 and 2024 Diff max Sen Median - difference in the maximum ranges based on the provided median from dev.bg for a category between 2023 and 2024

38

Do you hire developers based on technical skills alone? It could be costing you.  Many companies make this mistake, believing that if a developer can code well, they’ll automatically thrive in the team. But this is not always the case. I have a client in Krakow who specifically hires Java Engineers who can have a “normal conversation" about software, clean code practices, and general life. But most importantly someone he can get along with. If they can do that, he’s usually ready to hire them. However, if they don’t fit culturally, it doesn’t matter if they’ve coded at Google, have an Oxbridge education, or have a long list of technical achievements. They won’t get the job. This is also not unique. According to Leaders.com, approximately 80% of employers take personality into account when making hiring decisions. Also research from Harvard Business Review found that 40-60% of hiring managers admit to hiring candidates who resemble them in terms of background, values, or attitudes. None of this mentions their skills. The ability to mesh with the team and collaborate is non-negotiable. Some people picture developers as introverted hackers, coding away in dark rooms, surrounded by empty energy drink cans. The stereotype that developers don’t need social skills in my opinion, comes from how they’re portrayed in Hollywood (Die Hard 4 was what came to mind when writing this). In reality, developers are part of cross-functional teams. They interact with product managers, designers, and other stakeholders daily. They need to explain complex ideas, collaborate on solutions, and contribute to the team’s overall culture. A developer who can’t work well with others or communicate effectively can disrupt workflows, no matter how technically gifted they are. It’s like having the most advanced software that no one knows how to use. What’s the point? The best hires are those who fit into your culture and can contribute to the team dynamic - not just those who can write the cleanest code. So if you’re only hiring based on technical skills, you might be missing out on your most valuable assets: collaboration, communication, and cultural fit. Skills get you in the door, but culture fit keeps you there. Do you take culture fit into account when hiring engineers?  #SoftwareEngineering #PolandTech #TechRecruitment #PolandJobs #CultureFit #DeveloperLife #WorkplaceCulture #TechRecruitment

4

Pragmatic approach to DDD with Spring Boot by Maciej Walkowiak. Highly recommended to watch before you start to overcomplicate your design: #keepITsimple

58

In the last couple of weeks, I have had many conversations with Krzysztof Przekwas and Artemi Krauczanka about the critical values of Software craftsmanship. For me: - Code should be simple and readable for all seniors and newbies in the project. - When unnecessary, try to avoid complicated patterns; maybe Kafka or MediatR is an overkill for your project. - You may have a tiny domain, or you built a simple integration to connect two systems, so it is stateless, mainly integration via REST API on the left and right site. - Remember there is a development phase and maintenance - is your code ready to be maintained? Thank you, Isaac Abraham, for the slide on the presentation (and also for the presentation about Functional Programming on .NET - The Best of Both Worlds https://lnkd.in/eiwzFUZe) PS> As a side note, I'm also in the phase of my career to merge services to optimize cost or remove a lot of unused code from the projects, and you?

15

2 komentarze

Are your software engineers' salaries aligned with today's market? Since 2020, salaries in Poland have gone from predictable to, well, unpredictable. I’ll never forget placing a Senior Ruby Developer for 13.5k PLN/month (B2B) back then. Fast forward to today, and that figure feels like a distant memory.Figuring out what to pay engineers isn’t as easy as averaging job board numbers (I wish it were). If you’re grappling with this challenge, here are three proven strategies to help you find the sweet spot: 1️⃣ Leverage Your Recent Hires Use data from the last 6 months. - Focus on salaries from closed contracts - interview figures only tell half the story. - How often have candidates been willing to commit to your offers? - Numbers from signed agreements paint the most reliable picture. 2️⃣ Listen to Engineer Feedback - Track how candidates respond to your offers: Are your salaries getting a thumbs-up or silence? - Does raising your range increase applications? - How challenging is it to close candidates at the current rate? 3️⃣ Consult a Niche Recruitment Partner - They’re in touch with engineers daily and know what works now- not last quarter. - They track salary trends across clients and can pinpoint real-time benchmarks. - Best of all? They will share this info for free.

3

Candidates asking salaries and negotiation strategy tips. Whether you are negotiating with a new employee or freelancer, or one of your existing developers are looking for a raise or are due for a review, it is essential to be prepared. This will help you make an informed offer; ensuring you are being competitive in order to attract or retain talented developers by paying a fair market rate, whilst not being taken advantage of. Negotiation strategy might differ depending on number of factors: - When was the last salary raise? Has anything special happened since then? - Current geopolitical situation in the employee’s country - What is your local employment market like for this role? Do you have lots of suitable candidates available? - How long have they already worked in your company? - How long have they stayed in previous roles? - How much experience do they have? - How critical is this person to your project/company? - Do you need the skills they have and are using within your project / company, or are you over employing? - How easy will it be to replace them with a new hire? - What kind of employee are they? - Do they deliver? - Are they a good resource? - Are they reliable? - Do they have a proven track record yet? Before you begin any salary negotiations, familiarize yourself with the current market’s situation so that you can assess how much other companies pay developers of a similar level in your local area. If you want to have a rough overview of these ranges you can start by checking levels. Websites such as fyi (which can be seen in the link below) gather data points from engineers all over the world to present aggregated information regarding salaries in the software engineering field. https://buff.ly/4cTbpdp Then the next step is to research positions offered by your competition either on one of job boards or directly on their website. That will give you a good grasp of where the market is heading and what expectations are reasonable. If you are already a bigger and established company (>35-50 people) you might already have some specified levels of seniority in your company so salary ranges are predetermined. In this case the objective of the interview process is to determine the candidate's level, which will enable you to know what room you have for negotiation. It is important to also take into consideration the location of the given person. For example, a salary might differ for a Software Engineer with the same skill set in Poland and in Ukraine. #EasternEuropeDevelopers #TechInCEE #DigitalTransformation #DevelopersContracting

5

What is Lean DevOps, what problems does it solve, and how can it be implemented in organizations? 🔄 Learn everything from Karolina Ochlik (she/her)'s guide! You'll see Karolina on our stage again this year, speaking about Agile. Who will be joining us? Register now ➡️ https://devopsdays.pl/ #DevOpsDays #Warsaw #DODWarsaw #DevOps #DevOpsCommunity #ITconference #JoinUs

5

Why can software developers be obsessed with making things perfect, as if they only have one shot at it? Where does perfectionism and decision paralysis come from? 🤔 I often think about Alberto Brandolini's words "Software development is a learning process, working code is a side effect". Indeed, the parallels between learning and software development are extraordinary. You cannot approach learning something new with an all-or-nothing attitude. You need experimentation and time to build understanding and internalise the knowledge so that you can apply it every day. Before you get there, you'll be riding the waves of partial understanding. That's all right. As a trainer, I design exercises to guide you gently through the process, sometimes using nasty tricks like "lies for children" 🫣. These are simplifications to get someone through simpler exercises until they are ready for something more challenging. But in software development we often simply lack knowledge. We lack a deep understanding of a domain we are working in. We lack skills. We lack knowledge of non-functional requirements. So it is impossible to code the perfect thing in such a position. We learn all these things on the job, but they are not immediately "available". That's why we do larger and larger refactorings - to reflect our better understanding of the domain in code and architecture, to use newly acquired skills, or to meet new requirements. On Tuesday, thanks to the hospitality of BEC Poland, I'm giving a talk on this topic at the DDD-WAW meetup https://lnkd.in/dcfnZJwy

10

1 komentarz

DevOpsDays Warsaw are comming! Join us in November, and enjoy the great sessions (I know they will be great, I helped to select them :D ) and use this time to meet new people, talk with them and enjoy the conversations during Ignite talks and Open Spaces! Especially these two - Ignites and Open Spaces are for YOU! And enjoy my video, which I created, first time, with AI :) Well, the idea was mine, always something :) https://lnkd.in/dA48hbWQ #devopsdays #devops #devopsdayswarsaw #community #ai #openspaces #ignitetalks

21

2 komentarze

I think we can call it our DevConf.CZ tradition that we always come up with some fun idea for a session with Tomáš Tomeček. 😊 This year, we run a meetup for open source project maintainers and as it was not recorded, we decided to share some best practices we heard during the meetup in this blog post. Any more tips for maintainers out here? Let us know! 💡

32

Geeknauts switches to Apropo for their project estimates! 👏 👏 👏 ➡ Geeknauts, a custom software development company based in Krakow, Poland, can be definitely counted among t͟o͟p͟ 5͟ ͟#S͟a͟a͟S͟ ͟s͟p͟e͟c͟i͟a͟l͟i͟z͟e͟d͟ ͟d͟e͟v͟e͟l͟o͟p͟m͟e͟n͟t͟ ͟c͟o͟m͟p͟a͟n͟i͟e͟s͟ ͟i͟n͟ ͟P͟o͟l͟a͟n͟d͟. They know very well all the different aspects of #SaaS business - both technical and business. ➡ What I however like the most about them, is their strive for perfection. They are not satisfied with solutions that are “𝘨𝘰𝘰𝘥-𝘦𝘯𝘰𝘶𝘨𝘩”. 🔶 That’s one of the few things that I always find common for all the A-Performers - they N͟E͟V͟E͟R͟ tolerate mediocrity. And that’s the main reason why Geeknauts switched from Google Spreadsheets to Apropo - they didn’t agree for mediocrity in their estimates and proposals. 📣 Here’s what Borys Z., Frontend Developer & Sales Representative at Geeknatus, says about the impact from implementing Apropo: “Apropo 𝘀𝗶𝗴𝗻𝗶𝗳𝗶𝗰𝗮𝗻𝘁𝗹𝘆 𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗲𝗱 𝗼𝘂𝗿 𝗰𝗵𝗮𝗻𝗰𝗲𝘀 𝗼𝗳 𝘄𝗶𝗻𝗻𝗶𝗻𝗴 𝗺𝗼𝗿𝗲 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 thanks to creating estimates that look 𝘄𝗮𝘆 𝗯𝗲𝘁𝘁𝗲𝗿 than Google Spreadsheets. The way how estimates done in Apropo look also massively helped with communication with our clients and 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗵𝗲𝗶𝗿 𝘁𝗿𝘂𝘀𝘁. Our 𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲𝘀 𝗮𝗹𝘀𝗼 𝗴𝗼𝘁 𝗺𝗼𝗿𝗲 𝗮𝗰𝗰𝘂𝗿𝗮𝘁𝗲 which further helped us increase the profitability of our projects” 🤝 Thank you Borys and Geeknauts Crew - it’s a pleasure to have such A-Players like yourselves as our users. We wish you tons of time saved, accuracy increase and deals won with Apropo!

28

If you are curious on "Evolutionary Architecture" don't miss our .NET User Group Zürich May Meetup where we will cover the topic providing some lessons that diverge from "pure tech" talks. On this one, Maciej Jedrzejewski will explain How incremental developments in core engineering have enabled the foundations for enable software which can evolve over time along the architecture, protecting important architectural characteristics as it evolves. All while keeping it as simple as possible, maintainable and manageable in amount of complexity. Sounds interesting? ;) It is!! And even more if you have 5+ years of experience, chances are that you have lived a project that died because of complexity and lack of proper architectural vision (partial or... complete) - I've been there! So, how does it sound and all of this - for free!! Thanks Digitec Galaxus AG and Maciej Jedrzejewski!!! I am not going to miss it - and so should you... RSVP while you can, places are limited: https://lnkd.in/dmnnEGUZ Ah, we will have Food & Drink #architecture #software #evolutionaryarchitecture #KISS #DRY #easy #maintainable #resilience

Yesterday, Krystian and I presented at the QA Meetup at StoneX Poland in Krakow. I talked about the progress in AI and how it is changing the way we develop automated tests, with demos using Testim and ZeroStep/Playwright as examples. My sincere thanks to everyone for attending. What can I say, it was a real meetup with tough questions, very interesting discussions and people with expertise in QA topics. I'm looking forward to more such events, and I think there will be some ;) #QualityAssurance #AI #Testing #TestsAutomation

61

Another expert in the DevOpsDays Warsaw team is Andrzej Grzesik. ags loves distributed systems in all shapes and forms. He has written software in many languages and continuously finds JVM his favourite platform. He believes „most software problems are people problems”, so he stirs communities (Polish JUG), organizes and speaks at conferences (proud to be a JavaOne Rockstar!). Call For Papers: 👉 https://lnkd.in/dAiXrquA #DevOpsDays #Warsaw #DODWarsaw #DevOps #DevOpsConference #Community #Organizers #CallForPapers

63

💼 Excited to share my latest article on Golang Developer Salaries in Poland! 💰 I’ve broken down the latest salary ranges in Poland and compared it with the salaries in the top tech destinations worldwide. 👉 Check out our article here: https://lnkd.in/d8gzvYhp #Golang #Salary #TechSalaries #Poland #IT #Itentio #ITRecruitment #TechRecruitment

8

1 komentarz

Hello colleagues, My good friends 🌟Fwdays will organise great event in Warsaw, Poland. This is a short of overview of this : Meetup dedicated to microservice architecture and solving the most common issues using real project examples. You will learn whether microservices are always a magic bullet for your project and how to use this popular technology without harming your product. 🕖When? June 27 at 6:00 PM. Entrance is free with a donation to the Military Medical Rehabilitation Fund. 📌Where? Emilii Plater 53, 00-113 Warsaw. 👉🏻Registration and details: https://bit.ly/3XfXryc 🇬🇧Event and presentation language: English. 🗣 Alim Ismailov, Lead Software Engineer at Sigma Software, will share his experience on the topic: Microservices as Distributed Systems. You will see interesting and useful cases from real projects and learn how teams overcame various challenges during microservice implementation. 🗣 Oleksandr Hilevyi, Architect at Creatio, will explain why microservices are not always a magic bullet. He will discuss costs, scenarios where services can break themselves, and how to use the technology wisely. After the talks, there will be pizza and gifts! And, of course, networking, where you can meet your peers. BTW, You can join the Fwdays Poland Telegram chat for communication: https://lnkd.in/ddBBHg7j

19