Ilia Pavliukov

The worst code I worked with sold for $700M It changed how I see tech: I was an idealist: • Clean code • Thorough testing • Best architecture possible When I saw the news, I realised I was wrong There was value in • 2 enormous PHP monoliths • Integrated over database • Without tests The business made $1B in trades. The software was just an automation. Business value > Tech purity

6,081

694 Comments

DevOps is not a Job Title, it's a mindset/philosophy. This is how we will know if that debate has finally been won. The 390,000 DevOps Engineers on LinkedIn will change their job titles. Until that happens, sorry but it is a valid Job Title. (Even if I prefer SRE, Platform Engineer, Cloud Engineer, or Backend Developer.) #devops #sitereliabilityengineering #platformengineering #cloud

9

2 Comments

𝐍𝐚𝐭𝐢𝐯𝐞 𝐇𝐓𝐓𝐏'𝐬 𝐢𝐧 𝐆𝐨𝐥𝐚𝐧𝐠! 💡 Another new and interesting article to dive into around Golang! https://lnkd.in/ea5gYBVt As always please leave any impressions and thoughts in the comments! 😁

22

1 Comment

Which companies are employing the most Kotlin Developers in the UK? 👨🏼‍💻 1) JPMorganChase (526) 2) Meta (493) 3) Tata Consultancy Services (430) 4) Google (414) 5) Amazon (361) 6) Sky (319) 7) Lloyds Banking Group (280) 8) Arm (260) 9) Goldman Sachs (235) 10) Cognizant (217) #LinkedInTalentInsights

15

Hej Network! Java 23 came out couple of months ago now, if you haven't had time to catch this might be helpful. As it's not a LTS like Java 21 which is growing in the market for Java code bases. Mostly the features are a refinement in this version with some new stuff also. A run down for people that want know about the key features, do your own research for all the details. ⏺️Pattern Matching Came in Java 17, allow more complex use cases with deconstructing data ⏺️Structured Concurrency Been around since Java 19, but improved stability from older versions. ⏺️Virtual Threads Again, came in Java 19 and gives better resource management better to use in high Concurrency applications ⏺️Record Patterns First came to Java in this form in 16 and allows are to extend record patterns and deconstruction of record types. Mainly improvements from version 19, 20 ad 21. New features are! ❇️Module Import Declarations  Simplified import of entire modules ❇️Markdown Documentation Comments Write JavaDoc comments using Markdown 💠Generational Z Garbage Collector (not completely a new thing, but due to its new generational mode in 23 it's a good thing. Also, Java 24 not too far away so keep an eye out for that! #Java23 #Java

17

Sometimes when we think about technical debt, the immediate reaction is to want to stamp it out. Fix things, upgrade everything, refactor. Now. But sometimes you have to pause and ask: will an application gain value when we refactor it? Try flipping that question around: does a badly written app have enough value that it's worth refactoring? Maybe that's the question you need to ask.

16

First, I have an doubt how these containers, pods and services will communicate with each other and later this communication is called as "Kubernetes Networking". when I am preparing kubernetes I did not notice that much about kube proxy and CNI pluggin. But, later on I came to know that without these two communication is impossible. communication between containers in pod: containers use pod IP for external communication and for internal communication it uses local host and the port that container exposes. communication between two pods in same node: CNI plugged establishes the bridge network and this is connected to the multiple network of the pods in the same pod. so each pod will have a virtual ethernet interphase. so when pod A wants to communicate with pod B. pod A creates a packet with destination IP address and sends it to the virtual ethernet interphase of pod A, as both pods network interface is connected to the bridge network. the packet will travel through the bridge network to the virtual ethernet interphase of pod B. from here packet will travel to pod B and this packet will be processed by pod B and communication is established.

1

Programming tests are: ❌ Often stressful ❌ Take-home tests are usually time-consuming ❌ Rarely representative of the approach and conditions of the job that they're testing for ❌ Many times online code testing platforms will penalise you for clicking away from the screen and sometimes they penalise you for any copying and pasting ❌ Usually theoretical "best practice" based - showing how you might do something if you were working in a vacuum, not accounting for business needs / interdependencies with legacy platforms etc ❌ Typically they favour those who have more recently come from education over more seasoned professionals ❌ In some cases the results are ignored or overlooked anyway if the candidate has done well enough in interviews rendering the test itself pointless ❌ In other cases companies take a "line in the sand", "computer says no" approach where even someone who is a known entity to the team or business will be rejected if they don't do well enough on the test   I have NEVER heard a developer say that they enjoy technical tests.   Some of the most senior, capable, accomplished developers I have worked with refuse to complete them as part of a process - particularly timed ones.   How often do you write code in a real life production environment with a timer counting down? And when would you ever want your team to not have access to Google or GitHub or Stack Overflow on a difficult task? A significant part of an Engineer's role is to research potential solutions critically, not to be a walking programming encyclopedia!   Even if your test is a less pressured, more representative take-home task rather than a recorded or monitored time-pressured task, they're not always that informative and they often take up a large chunk of time, which, particularly for someone who is currently in full-time employment and interviewing for multiple other opportunities, is a lot to ask. They also often lead to excellent candidates withdrawing from the process.   To quote a senior dev I spoke to the other day: "It doesn't matter how great the pay or the company or the work are. I'm a professional with over 10 years' experience, treat me like it. Don't set me bullsh1t homework"     👉 So why is it that so many interview processes use them? 👉 And what are the genuine legitimate alternative approaches to be able to ascertain someone's technical capability?   Keen to hear your thoughts Linkedin? Futura Talent #technicaltesting #techrecruitment #developerlife #softwaredeveloper #softwareengineer

8

2 Comments

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

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 Comments

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 Comments

At what stages pods will fail and a new pod is created with a new ip address * During scaling and replica operations pods will be terminated. * when using deployments, while updating the image version the pods are terminated and new pods take the place of old pods. * pods are dynamic in nature they come and go on the k8s cluster and on any of the available nodes and it could be difficult to access the pods as the pod IP changes once it is recreated. So, if the IP address changes it is difficult to route traffic. In this case only service object will be helpful and it will provide static IP and it will connect to all the nodes and pods using " lables and selectors".

1

2 Comments

{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

🚀 Exciting news from Parasoft! 🚀 They've just released the 2024.1 versions of their top-tier testing tools, including Jtest for Java, dotTEST for C#, .NET, and DTP for testing analytics. Here are some highlights: ✨ Jtest Enhancements ◼ AI-powered test templates in Unit Test Assistant for more control and customization. ◼ Real-time test impact analysis directly within the IDE, giving developers instant feedback on code changes. 🔍 dotTEST Updates: ◼ Integration with OpenAI/Azure OpenAI Service for AI-generated fixes in flow analysis violations. ◼ Support for the latest CWE list (4.14) and improved static analysis configurations. 🛡️ DTP Innovations: ◼ Accelerated security vulnerability remediation using AI, matching rule violations to known vulnerabilities with probability scores. These advancements are designed to streamline our workflows, enhance accuracy, and save valuable time. What do you think❓ #SoftwareTesting #Java #CSharp #DotNet #AI #Parasoft #SoftwareEngineering #CoreTalent #WeAreCoreTalent #Software #SoftwareJobs #SoftwareDevelopment

12

1 Comment

I'm sorry to break it to you 😞 A GitHub link may have been enough to secure an interview a few years ago but times have changed. CVs are being closely reviewed, and companies are demanding quality over quantity. It's time to delete Office 2003, and trim down the exhaustive list of every technology you've ever come across. Having recently connected with 100+ exceptional software engineers during a search for a leading European startup, I've noticed a clear pattern in what makes CVs stand out: 1) Impact matters more than ever! - Don't just list what you used - show how you shaped products - Highlight the "before and after" of your contributions - Quantify your achievements wherever possible 2) Showcase your achievements! - Led the migration that cut infrastructure costs by 40%? - Built and launched that critical feature used by millions? - Mentored junior developers into senior roles? - These are the stories that matter. 3) Personal achievements matter! - That side project you launched? Include it - Teaching yourself Mandarin? That shows dedication - Your top 1% ranking in competitive programming? Absolutely relevant The tech market is currently more competitive than we've seen in recent years. Don't let a poorly structured CV be the reason you miss out on your dream role. 💡 Need a template designed specifically to highlight these elements? Drop a comment or DM me - I can share a free CV template that's helping engineers showcase their true value. #SoftwareEngineering #Careers #Hiring #CVTips #Recruitment Kioni Talent

77

46 Comments

𝙄𝙨 𝘿𝙚𝙫𝙊𝙥𝙨 𝙗𝙪𝙧𝙣𝙤𝙪𝙩 𝙖𝙘𝙩𝙪𝙖𝙡𝙡𝙮 𝙖 𝙩𝙝𝙞𝙣𝙜? 😵   Are we in the middle of the Great DevOps Burnout? A report from Haystack suggests - 𝙔𝙀𝙎.   83% of the 258 software engineers surveyed reported feelings of burnout from high workloads, inefficient processes, and unclear goals and targets. 74% of software engineers surveyed reported working on operations tasks in some capacity.   Another survey from Spacelift follows a similar theme (𝘒𝘌𝘠 𝘍𝘐𝘕𝘋𝘐𝘕𝘎𝘚 𝘚𝘏𝘖𝘞𝘕 𝘍𝘙𝘖𝘔 𝘛𝘏𝘐𝘚 𝘚𝘛𝘜𝘋𝘠🔎).   They found that “DevOps engineers are more frequently stressed than the IT average. Over 40% admit to being stressed ‘often’ or ‘very often’ compared to 34% of the IT average.” The study suggests that DevOps are the most stressed because they feel their skills are insufficient for their jobs.   Are their skills insufficient or does their setup lack a platform that provides sufficient support❓   In other words, it seems that a lot of folks “doing DevOps” are also burnt out. I think we have more research to do before we pinpoint the exact causes of this stress. But I don’t think the trend is a coincidence.   There is a growing conversation in the DevOps community about whether developers can or want to take on operations tasks. The main problem they’re encountering is cognitive load, which prevents developers from focusing on developing features and delivering the most value to the company. The organisation’s efficiency suffers as a result, and likely the developers’ well-being too.   Are you feeling the “Great DevOps Burnout”❓ If not, what is your organisation doing well❓ Cubiq Recruitment | #devops #platform #developer #burnout

24

1 Comment

"You interview all your software developers face to face?" 🧑‍💻🗣️🤝 There doesn't seem to be a uniform opinion on how interview processes should be structured, what should be online, and what should be in person. Personally, I like the hybrid process. Early stages take advantage of the efficiency of Virtual Interviews. Late stage(s) take the opportunity to invest in quality, dive deeper, and establish connection only possible with face to face meetings. An interview process exclusively online misses out on the opportunity to gain further buy in from your prospective employee. Show them what the work space looks like. Shape up what the commute will be like. Build some human connection. (Personally, I don't know how I would feel accepting a role and putting my career in the hands of people I haven't even met yet!) An interview process exclusively in person will result in slower turnaround times, and risk top candidates dropping out from a lengthy, and consuming process. What interview structure works best for you?

11

2 Comments

Over the weekend I re-implement my Rust Linux scheduler fully in C/BPF (https://lnkd.in/dZdw8fRG) removing all the kernel/user-space interactions. The BPF implementation shows a ~5% improvement, meaning that the user-space/kernel overhead is definitely not the main bottleneck!

143

6 Comments

99% of CTOs I speak to avoid hiring software engineers for this reason: If you can’t: > Accept constructive feedback > Talk about a project that went wrong > Take accountability for mistakes > Acknowledge contribution of others It’s time to reassess- fast Less ego, more modesty

16

9 Comments