Bartosz Rybacki

I'll be talking about building future-proof React applications on the 30th of May in Bucharest. Everyone needs to have a set of principles they follow so they don't have to think about every problem from scratch. I'll tell you how I've been building React applications for the last 8 years. What works. What doesn't. What to focus on to make sure you don't have to rewrite your application every year. Because programming is about solving problems. But engineering is about maintaining those solutions over time.

100

3 komentarze

Supercede programmers at Lambda Days conference in Kraków, Poland 🇵🇱 I thought I would win the most-appropriate-tshirt contest, but I think Luke has the edge on that one. I gave a quick lightning talk on primitive obsession in persistent types. Long story short: you should be using `checkMMap` liberally in Yesod forms, and your persistent types shouldn’t contain a load of primitives. Otherwise those primitive values float through your system and there are many more places for things to go wrong. #haskell #functionalprogramming

34

Developer Experience is still a problem! I listened to this podcast https://lnkd.in/eZPvJnGE on how LastPass tries to make local experience much easier in the area of microservices. They went from the usual suspect of Docker compose but it requires you to build Docker images before being able to run things. Then they went to local kubernetes but it adds another layer and it doesn't help with the extra Docker build step. They decided to use nix which is Docker without Docker, universal package manager. This is something I looked at when working on codefly agents. One goal of codefly is to provide great Developer Experience, a developer starts any service, it will run any dependent services, do all the networking, and even provide hot-reloading for languages that don't have it (golang for example). I found nix to be too complicated so I am relying on Docker and spent quite some time getting that right: you really don't want to start/stop containers all the time and it's actually not that trivial to start and stop processes inside a Docker container. But the pain is worth it: - dependency is minimal, Docker is OK, nix is another story - performance hit is minimal since we try very hard to keep the containers around And agent can also use local stack if available. The philosophy of codefly is that your code needs some "co-pilot" for everything from setup, package maintenance, to networking, Docker build, kubernetes manifests. We do all the annoying stuff so you can just focus on writing code, writing tests that can depend on your full stack without any change of code, or mocking -- just that is a game changer and that's it. We take care of all the painful stuff so you can do the fun stuff!

1

I could not agree more. Recent articles about "ghost developers' based on the number of GitHub commits reflects an incorrect perception of how hard software developers working in different roles. I was also annoyed by the notion that somehow, there are 10% of developer's 'coasting' and getting paid hundreds of thousands. This happens in all industries not just software development. https://cstu.io/d41234

3

2 komentarze

1. Gradle Inc. Gradle is like a magic builder for your software projects. Think of building a house - you need to assemble bricks, wood, and other materials. Gradle does this for software. It takes your code, puts all the pieces together, and turns it into a working app or software. It's super fast and can handle big projects with ease, making sure everything is in the right place. 2. Phabricator Phabricator is like an all-in-one project hub for software development. Think of it as a digital workshop where your team can plan, build, and manage projects together. It helps you track tasks, review code, and collaborate in one place. This makes sure everyone stays on the same page, work moves smoothly, and projects are completed efficiently. 3. Gitea Gitea is like a digital storage locker for your code, but with teamwork in mind. Imagine working on a project with friends. You all need to keep track of who did what and make sure you're not messing up each other's work. Gitea helps you do that by letting you save your code, track changes, and collaborate seamlessly. Plus, it’s lightweight and super easy to set up! 4. Huginn Huginn is like your personal internet assistant. Imagine having a smart robot that watches the internet for you and takes action when something happens. Huginn can send you alerts, gather information, and even perform tasks automatically. Whether it’s monitoring news, tracking emails, or managing social media, Huginn makes your online life easier by doing the repetitive work for you. 5. Tabnine TabNine is like an intelligent assistant for coding. Let's say you’re writing a long essay, and someone whispers the next sentence to you. That’s what TabNine does for coding. It predicts what you’re about to type next and offers suggestions, helping you code faster and with fewer mistakes. It’s like having a smart friend who knows exactly what you need. 6. Ansible by Red Hat Ansible is like a remote control for your IT tasks. Imagine having to cook dinner for 100 people in different kitchens. Ansible helps you control all the stoves from one place. It automates tasks like setting up servers, deploying apps, or managing systems, so you don’t have to do it manually. It’s super efficient, reliable, and saves a ton of time. Follow For More 🤖

6

2 komentarze

When I first started with Clojure, it essentially meant working within the JVM or JS ecosystems, with all their benefits and drawbacks. Since then, the landscape has changed a lot. Babashka came along, effectively replacing Bash and Python for me in 90% of use cases. Then there was ClojureDart, making mobile app development much easier—something that was never a walk in the park with Clojure before. I also discovered Basilisp, which compiles Clojure into Python, expanding its reach even further. Scicloj is another great project, with Daniel Slutsky pouring a lot of energy into it. Today, I wouldn't hesitate to use it for analyzing complex data, unless I specifically need a library that's only available in R or Python. And now, with Jank from Jeaye Wilkerson (who has years of experience building game engines for EA), we’re about to be able to use Clojure with C++ as well. This opens the door to high-performance, native applications. Clojure is (becoming), in my opinion, the most versatile modern language out there.

15

1 komentarz

{let xmas_spirit=true} 100% off our `Personal Performance` course (until Thursday 12th December) Code: "REVIEWIT" https://lnkd.in/eQ5tYTFV PLEASE ADD A SHORT REVIEW AS A COURTESY. Thank you very much in advance. Truth. 100% off! Enjoy. ;-) 👋🏾💪🏾2️⃣0️⃣2️⃣4️⃣ #techlead #Techlayoffs #developers #java #personal #career You have until Thursday 12th December 23:59 to register for free at no financial cost to you. In return just write a brief one to three sentence review of our work. I will collect the feedback to create a brand adventure in 2025. Note: there is limited availability on promotion codes, so when they are gone they are gone. Merry Xmas from moi!

3

I was recently reading Gergely Orosz's interesting blog in Pragmatic Engineer about how Brooks' "The Mythical Man-Month" holds up after 50 years. Great summary of the key points on estimation and how developer productivity has changed with high-level languages. (🔗https://lnkd.in/dbPR_dFq) But I want to add a few thoughts on the focus on lines of code (LOC) as a productivity metric. LOC is a relic of the 70s! Sure, developers today churn out way more lines than back then, thanks to modern tools and languages. But as Gergely mentions, counting lines tells you nothing about the code's quality or business value. A developer fixing a critical bug with 10 lines might have a bigger impact than someone churning out thousands for a rarely used feature. Another factor is that LOC is something that we fight against. We want to be able to express the same concepts with less code. A Pull Request that deletes 10,000 lines of code actually adds value to the project. That is less work to maintain, understand and work with. Here's what I focus on for developer productivity: Did the code solve a real problem or improve the product? Is the code clean, easy to understand, and modify? How quickly can a developer iterate and deliver working features? And we cannot forget the unsung heroes! Developers who spend hours analyzing performance or designing solutions might not write tons of code, but their contribution is crucial. 📷 This image, 160 LOC added to RavenDB - represents about three months of work by yours truly (pretty senior guy, 20+ years experience). As a metric, it tells us basically nothing. If we are looking at lines of code added to the project, that is abysmal rate compared to the time taken. ‌Of course, that change removed three separate lock convoys, simplified cross platform build and unlocked at least three new features… 🔑 Focus on building high-performing engineering teams, not on individual LOC. #developerproductivity #softwareengineering #dreamteam #Coding

45

7 komentarzy

🚨 4:23 AM: The Battle with Gradle 🚨 Yes, it’s 4:23 AM, and I’m still here, battling through a stubborn "Gradle Error" that decided to crash my app build. Hours of effort—updating plugins, tweaking gradle-wrapper.properties—and finally, the app is back on track. Coding isn’t just about knowing how to fix things; it’s about persistence, patience, and understanding why issues happen. Tonight (or should I say this morning), I pushed through, learned a ton, and emerged a little stronger as a developer. Sometimes the late nights pay off in lessons learned. Here’s to the grind and the growth that comes with it. #code

45

3 komentarze

Who do I know that uses or has used Apache Beam it looks pretty interesting after the talk from Oleksandr Saienko at #PyConIreland i would love to talk more about it with anyone experienced.

2

Probably I am not the only one that tries to find some spot here and there to do a bit of reading (specially if you have 80 tabs open with "Save for later" articles 😅 ). In the IT field, being able to "catch up quickly", "learn quickly" and "solve quickly" is seen as a must to stay in the sector for the long run. To be honest, it is overwhelming. The constant focus on "quickly" can make us forget that real learning and problem-solving takes time and effort. This has deeply bother me for quite sometime and even make me feel unproductive, blocked to finish writing / creating things I had in mind for a while because I am already late for it. But when I take a step back and look at everything I've actually done, I realise I have been doing way more than I give myself credit for (specially given the amounts of hours a day has). It's just hard to see that when you are struggling in the grind. And honestly? It’s exhausting and confusing 🫠 It was a good timing then that Today I ended up with this article from the Hacker Newsletter: https://lnkd.in/dBKG7v7K and something resonated there: "I want to know everything, immediately, quickly. Since this is not humanly possible, I end up doing nothing." "You find yourself in a quest for productivity, feeling productive because of the quest, but not really doing any productive work." "Difficulty concentrating, lack of focus, inability to understand what I read, stress, anxiety. I see these kinds of complaints from many people lately, and in my opinion, our biggest common ground is digital content consumption." And avoiding, like the author, to go against that article, I also do not have an advice, but just leaving the article there for your own reflection on this. Slowing down, taking a break, and letting yourself process what you already know can be more valuable than rushing to consume the next thing. 🌱 Give it a read if this resonates with you. Ask yourself what would slowing down look like for you? I'm trying to figure out for myself right now

36

Many of us are working on exciting projects but only few succeed. During my attendance to two European Ruby conferences in June, I had the opportunity to ask top Ruby developers this crucial question: why do software projects fail? These are some great insights they shared on common pitfalls, unexpected challenges, and lessons learned from project failures . Watch my full video on my YouTube channel for more in-depth insights and discussions: youtube.com/@tillcarlos

6

WARNING ⚠ : Are you about to design or work on a microservices project? If so, you really need to read this first. I will be publishing a series of articles about the dark side of microservices projects, and how some tiny design mistakes can grow into huge problems 🌋. My point of views are up for debate. I'm not saying I'm right, rather I'm showcasing some of the problems I went through. If you have an opposing opinion please share it with me as these discussions can help both of us learn more 📚.

6

I wrote a new blog post about my experience at ApacheCon - ASF Events Community Over Code, Outreachy and what it's like working at Percona, and the cool cloud-native tool for databases on Kubernetes that we are working on right now: Percona Everest, open-source! 🤗 👩‍💻 💃 🕺 https://lnkd.in/djdCxXea If you have any questions about any of these topics, send me a direct message so we can have a virtual coffee! ☕ #databases #cloudnative #opensource #kubernetes

28

1 komentarz

Knowledge Sharing: Day 22 Breaking change if you are planning to upgrade your compileSDK to Android 15 or higher 📢 If you use Kotlin's list.removeFirst() or list.removeLast() extensions in your Android app, then, after bumping compileSdk to 35, your app will crash at runtime on older Android versions. #android15 #android #behaviour #development Kaara

34

3 komentarze

Minimal API is... SPEED & POWER :) DevNetwork thx so much for having me as a speaker SoftwareHut thx for the support

14

2 komentarze

Episode 430 - How Short String Optimizations Work https://lnkd.in/ga5AkNvJ

72