Granit Gjevukaj

Embedded developers with niche skills are like gold dust. If you find one, don’t hesitate... hire them quickly. I see over and over that these specialists are often snapped up by companies that understand their value. That means your hiring process needs to be not just fast, but also enticing. Competitive salaries, interesting projects, and a clear path for career growth are essential if you want to attract and retain this top talent. Speed and flexibility in hiring can make all the difference 🙏 The companies that adapt their recruitment strategies to move quickly are the ones that will come out on top.

3

Why do we need background tasks in .NET? Scalability and responsiveness are a few good reasons. I want to move some work in my application to the background. I want this background work to run outside the normal application flow. Here are a few examples: - Sending an email after completing a sale - Processing messages from a queue - Clearing stale cache items Let's take the example of sending an email after a sale. I don't want to slow down the API response by waiting for the email sending to complete. Instead, I can queue an email and process it in the background. You can set up a background task in .NET within minutes. The most straightforward approach is using the BackgroundService class. With .NET 8, we can also start these background services concurrently. P.S. Every Saturday morning, I send one practical tip to 56,000+ .NET engineers to help them grow their skills. Join free here: https://bit.ly/4eZg8fa What do you think about the built-in support for background jobs in .NET?

926

47 Kommentare

lateinit and lazy in Kotlin Imagine you’re at a party 🍕, and you tell your friend, 'Bro, you’re on snack duty, but don't bring them right away. We’ll call for snacks when we really need them.' That's lazy in Kotlin! You don’t initialize a variable until it’s actually used. It’s like telling your code, 'Hold up, I’ll get to it later when I need it.' val snacks by lazy { fetchSnacks() } Then there’s lateinit – it’s like inviting a DJ 🎧 and saying, 'Yo, I’ll tell you where to set up later, but trust me, I’ll need you.' Here, the variable is initialized later in the code but must be initialized before it’s used. lateinit var dj: DJService In short: Lazy: 'Bring the snacks when I need them.' 🍿 Lateinit: 'I’ll set up the DJ before the party starts, but not just yet.' 🎶 Now the next time you see lazy or lateinit in code, you know they’re just like party prep! 🎉 #Kotlin #LazyVsLateinit #CodingAnalogies #AndroidDevelopment #DevLife"

12

1 Kommentar

🔥 You can detect the render mode of the parent component in Blazor in the latest .NET 9 preview! The Platform property that the #blazor ComponentBase gets (check the last post) is not the only extension! We also get an AssignedRenderMode property and it opens another layer of possibilities in component-based architecture. 💡 What is the AssignedRenderMode? 👉 a property of the ComponentBase class 👉 allows determining the #rendermode defined in the component hierarchy 🔎 When is the AssignedRenderMode useful? 👍 especially in prerendered scenarios 👍 you can opt to disable interactive DOM elements during #prerendering 👍 for #interactive or non-interactive modes 👍 you can skip or render markup supporting specific browser mechanics 💭 Do you see use cases in your current code already?

13

Exciting news for developers!  🎉 Biome [https://biomejs.dev/] now supports CSS Biome has just released its latest version with CSS formatting support, a feature I've been looking forward to for quite some time. But it's not just about CSS – Biome is revolutionizing how we handle linting and formatting in our projects. Here's why I'm thrilled: • 🛠️ All-in-one solution: Biome gives you everything you need for linting and formatting your apps right out of the box. No more juggling multiple tools and configurations! • 🚀 Lightning-fast performance: Biome's formatting and linting are optimized for speed, significantly reducing development time. • ⚙️ Effortless setup: Configuration is a breeze with a single tool handling everything. Say goodbye to the complexity of managing multiple tools. • 🔄 Reduced conflicts: One tool eliminates rule conflicts between different linters and formatters. Your codebase stays consistent effortlessly. • 🎨 Comprehensive coverage: From JavaScript to CSS, Biome handles it all, ensuring a uniform coding style across your entire project. [https://lnkd.in/diaWN8iC] I've put Biome to the test in a real-world scenario! I've built a template for monorepos using Biome and other useful tools. If you're looking to kickstart your monorepo project with best practices and efficient tooling, check out my template here: [https://lnkd.in/dgmWijgy] I'm eager to hear your thoughts and experiences. Let's discuss how we can leverage these tools to boost our productivity! #biome #webdevelopment #typescript #javascript #css #developertools #monorepo #softwareengineering #frontenddevelopment #codingbestpractices #developerproductivity #techstack #opensource #webperformance #cleancode #developerexperience #techcommunity

8

Back with another #KirstysKotlinFacts ! 💡 Last week I spoke about the misconception that Google was the original creator of Kotlin. Here's another misconception. Kotlin was created for Android. Wrong. Kotlin was always designed with the intention to be used for server-side backend development, it just so happens that it's also good for mobile development. The push for mobile actually came from developers themselves. The already existing mobile language #Swift by Apple was not working quite as well as hoped/needed, so the community requested it in need of a better language for android. Android became their priority in 2014. So, despite the initial purpose of creation, nowadays if you tell someone you're a Kotlin developer, more often than not, they will assume that you're an android developer since Kotlin is now more widely known for its android use. Would you also make this assumption if someone told you they were a Kotlin developer? #Kotlin #Android #Backend #SoftwareDevelopment

11

Want to be ahead of the game as an application developer and secure your position in the market for the next years? Here is what you should focus on, and what you should not focus on...🥷 You should NOT focus on: -The newest framework -The sexiest thing -The best code -The most performant thing You should focus on: -Solving problems -Automation -Edge functions -Standards that can be interpreted by LLM's like TailwindCSS -Learning prompt engineering -Setting up RAG systems -Learning/understanding the basics of NLP -Playing with hugging face It will literally blow your mind

5

2 Kommentare

My ongoing projects include ParaPal (direct payment gateway), EsLa (fire alarm security system), and FlashCard (English language learning). #inprogress #native #development #singlepage #dotnet #netcore #aspnet #flutter

2

→ 11 years ago: I started coding seriously to get a job → 9 years ago: I contributed first time on an opensource project while working at KoderLabs https://lnkd.in/dgR_UZSP - We never published it → 8 years ago: I published ng2-hz-datepicker while working at KoderLabs - https://lnkd.in/dqbsFr_Q - That's when I also founded IOMechs aiming to create one of the best consulting firms in Pakistan. → 7 years ago: I created and published ng2-device-detector (an Angular library for detecting what device you're running an Angular app on) https://lnkd.in/daxH6kC5 - Also while working at KoderLabs. And created my first contribution to an #Angular core repository: https://lnkd.in/ev7GT86 → 6 years ago: Published ngx-device-detector which has over 11 million installs today. https://lnkd.in/d_hKtbQc. Also, became one of the Google Developer Experts → 5 years ago: Created my first video course ever with Packt. I can assure you that wasn't a success :) → 4 years ago: Published my first book ever. Angular Cookbook (1st Ed): https://lnkd.in/d8cEsPnE → 3 years ago: Published some cool stuff with the good people at IOMechs. For example Pure CSS Loaded Extended https://lnkd.in/dCZTJrQ4. Created TypeScript Webpack Tailwind CSS Starter (https://lnkd.in/ddpyWWqB) and started taking my YouTube account seriously (https://lnkd.in/d3NXPE4y) → 2 years ago: I launched my FREE Web Development Bootcamp course (https://lnkd.in/d5vdafhe) → 1 year ago: I released the Web Dev Basics (FREE Urdu/Hindi) course for the people of Pakistan and South-East Asia (https://lnkd.in/du499xzf) → 2024: Released "Practical React Essentials Course in Urdu/Hindi"(https://lnkd.in/dSQH4HKT). Published my 2nd #Angular book (https://ng-cookbook.com). And started looking into AI and ML. As Wajahat Karim 🇵🇰 rightly said,  “𝗖𝗼𝗻𝘀𝗶𝘀𝘁𝗲𝗻𝗰𝘆 𝗶𝘀 𝘂𝗻𝗱𝗲𝗿𝗿𝗮𝘁𝗲𝗱 𝗮𝗻𝗱 𝗵𝗮𝗿𝗱 𝘄𝗼𝗿𝗸 𝗶𝘀 𝗼𝘃𝗲𝗿𝗿𝗮𝘁𝗲𝗱.” The Prophet (salallahu alayehe wasallam) said “Take up good deeds only as much as you are able, for the best deeds are those done regularly even if they are few.’ (Ibn Majah).  He also said. “The most beloved of deeds to Allah are those that are most consistent, even if it is small.” (Bukhari). I try to focus on being consistent and to be someone who puts in the time. Even if it is little. The outcome/goal is never my focus. And it seems like I'm doing pretty well :) Some things I wish I knew before that could help me be better. More in comments :)

167

11 Kommentare

I once had to experiment and try different payment providers to decide on the best one in a software project. There were 4 identified solutions and it was crucial to provide proof of concepts of at least 3 for the client. Traditionally this would have take months to implement as it would be 3-4 potential projects to develop. As solutions architect I proposed to use a completely #serverless approach to experiment with all 3 different solutions. It was hard to measure exactly but the time saved to setup the infrastructure, servers, provision #databases and write APIs would have been considerably long. Instead with the cloud (#AWS) I was able to deploy functions, a database and an API, which were all serverless, in under an hour. I used AWS IAM for API and database security and several other services to host and deploy the application. In the end, the speed of the proof of concepts was essential and in this industry I learned that nothing is more important. Customers never care about what tools/solutions I have ever used, only how much time it takes and how much it costs. With serverless services, cost was inexistant amd time was super short to demonstrate the different POCs. When you know how to use serverless, it empowers you. ---------- 📪 Join my newsletter "The Serverless Spotlight" to learn about cloud & serverless development. https://lnkd.in/eUaV8xsr

1

Slides and demo repo for my talk "Mastering State Management in Angular with the NgRx Signal Store" https://lnkd.in/emna6VyU at the iJS in Munich.

16

I still can't believe we have the `@let` statement in Angular ❤️ ! I've wanted it for years! It was always possible using the `*ngIf` directive to create a variable when working with the `async` pipe, of course. But creating any variable in Angular templates is probably something every developer has felt the need of, at some time in their lives. Well, it is finally here 🚀 I'm loving the updates coming to Angular in the past 2 years. And it just keeps getting better. . . . #angular #typescript #webdev #webdevelopment

105

5 Kommentare

One of my goals going forward was to write better code reviews instead of "LGTM". I recently discovered the MoSCoW technique to review code and presented the idea to my team this afternoon. In short, MoSCoW stands for: M: Must S: Should C: Could W: Would Here is why I advocated to implement MoSCoW technique: 1) Helps reviewer provide thorough feedback 2) Helps the team prioritize tasks before a release 3) Helps the coder understand if they reached their main task objective. After presenting it the team, we will be using the MoSCoW technique for the next couple of weeks and assess afterwards how everyone liked it. What are other code review techniques you used that we should implemented? Please let me know what your thoughts are. #MoSCoW #codereview #code #softwareengineer #womenintech #softwaredeveloper #gridironsurvivor #clientproject

24

1 Kommentar

The software development industry isn’t in great shape right now, and if we’re being honest, we have ourselves to blame. For years, the industry has been driven by ego. Companies raced to adopt the latest tech, desperate to stay ahead, no matter the cost. It became a game of being the most cutting-edge, even if that meant overpromising and underdelivering. But now, the consequences are catching up. Outbound efforts are falling flat. The sales process is dragging on. And inbound leads? Almost nonexistent. Why? Because companies are now aware of the body-leasing scams. Vendors are selling juniors as mids, mids as seniors, and it’s costing everyone. This is a wake-up call for the entire industry! It's time to rebuild trust by aligning our solutions with real business needs, not just the urge to be ahead of the curve.

28

3 Kommentare

Blogged: Safety and simplicity with LINQ - Working with the result pattern - Part 2 https://buff.ly/4fnYamT In this post I show how to clean up unreadable Switch()-based result pattern code using LINQ query syntax, giving both readability and safety #dotnet aspnetcore

47

𝗪𝗵𝘆 𝗥𝗲𝗰𝗿𝘂𝗶𝘁𝗶𝗻𝗴 𝗦𝗮𝗮𝗦 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝗶𝘀 𝗗𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 – 𝗔𝗻𝗱 𝗪𝗵𝘆 𝗜𝘁 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 As a software engineering manager in the SaaS industry, you know that finding the right talent is crucial. So does it frustrate you that the people you task with your recruiting do not understand that recruiting SaaS developers fundamentally differs from hiring regular software engineers? 𝙒𝙝𝙮 𝙩𝙝𝙚 𝘿𝙞𝙛𝙛𝙚𝙧𝙚𝙣𝙘𝙚? SaaS developers need a unique blend of skills and experience. They must be proficient in languages like JavaScript, Python, Ruby, and Node.js, and have hands-on experience with cloud infrastructure services such as AWS, Google Cloud, and Microsoft Azure. They also need to excel in API integration, database management, DevOps, and automation, and be adept with containerization technologies like Docker and Kubernetes. 𝙎𝙤𝙛𝙩 𝙎𝙠𝙞𝙡𝙡𝙨 𝙈𝙖𝙩𝙩𝙚𝙧 𝙏𝙤𝙤 Beyond technical prowess, great SaaS developers excel in problem-solving and communication. They can adapt to unexpected issues and find solutions quickly. Moreover, SaaS development is a team effort, requiring developers to work closely with designers, project managers, testers, and others. Effective communication ensures mutual understanding and alignment of technical decisions with every other aspect of the product. A top-tier SaaS developer can explain complex ideas to non-technical team members, fostering better collaboration and a unified approach to achieving common goals. 𝙏𝙝𝙚 𝘾𝙤𝙣𝙨𝙚𝙦𝙪𝙚𝙣𝙘𝙚𝙨 𝙤𝙛 𝙂𝙚𝙩𝙩𝙞𝙣𝙜 𝙄𝙩 𝙒𝙧𝙤𝙣𝙜 Hiring the wrong developer can lead to a product that is insecure, unscalable, and user-unfriendly. This not only affects your product’s performance but can also damage your company’s reputation and bottom line. 𝙒𝙝𝙮 𝙋𝙖𝙧𝙩𝙣𝙚𝙧 𝙬𝙞𝙩𝙝 𝙍𝙤𝘾𝙤 𝙍𝙚𝙘𝙧𝙪𝙞𝙩𝙢𝙚𝙣𝙩? At RoCo Recruitment, we specialize in identifying top-tier SaaS developers who bring not just technical skills, but a deep understanding of the SaaS landscape. We know what makes a great SaaS software engineer and how to attract them. Partnering with us ensures that your development team is equipped to build secure, scalable, and user-friendly products. Finding the right SaaS software developers is the only way to ensure your SaaS product is functional and competitive. Don’t leave it to chance – let RoCo Recruitment help you build a team that drives success. 𝘿𝙈 𝙞𝙛 𝙮𝙤𝙪 𝙬𝙤𝙪𝙡𝙙 𝙡𝙞𝙠𝙚 𝙩𝙤 𝙨𝙘𝙝𝙚𝙙𝙪𝙡𝙚 𝙖 𝙘𝙖𝙡𝙡 𝙩𝙤 𝙙𝙞𝙨𝙘𝙪𝙨𝙨 𝙩𝙝𝙞𝙨 𝙛𝙪𝙧𝙩𝙝𝙚𝙧 #Softwareengineering #SaaS #SaaSsoftwareengineers #RoCorecruitment #recruitment

4

I am currently building a Blazor app without the many advantages it brings for traditional ASP.NET developers. So basically as an everyday SPA. - No IdentityService to easily handle authentication and authorization. - No DbContext I can easily set up and inject - Token authentication, storing tokens in local storage. The reason for this is that I already have an existing ASP.NET application as an API and I don't want to mess with it or have to manage configs between both applications. There are a few other reasons but my point is I think things would be easier to manage this way. Good or bad idea?

1

Tip for Junior Software Engineers Avoid using "Junior" in your job title. It can give the impression that you lack confidence in your skills. The main thing hiring managers are looking for at your level is a positive, can-do attitude. Believe in yourself and your abilities!

29

4 Kommentare