Daniil Rabizo

I tried Uno Platform to build a quick tool for myself… and didn’t expect this. Turns out, building a real cross-platform app - desktop, web, and mobile - is way easier than I thought. I always thought Uno Platform was mainly for mobile - kind of like a Xamarin clone. But I was wrong. Uno Platform is a full cross-platform framework for: • Web (via WebAssembly) • Windows (WinAppSDK) • macOS, Linux • iOS & Android And it uses C# and XAML - perfect for .NET developers. I built a tiny Weather app and designed it live with Uno Platform Studio - no rebuilds. Uno Platform Studio (paid) is a companion that adds: • Hot Design (live visual designer on your running app) + Hot Reload. • Edits apply instantly and write back to your XAML. • With Hot Design you can change spacing, tweak colors, switch device sizes, and toggle light/dark while the app is running. • Real data, real states - what you see is what you ship. Under the hood it’s Uno Platform (open source). Uno Platform let me write one app in C# and XAML and run it: 1. As a native desktop app (WinUI) 2. As a mobile app on Android and iOS 3. As a web app (thanks to WebAssembly) And I didn’t need to change the UI code for each platform. Even better? The open-source tooling feels very familiar if you've ever used WPF or MAUI. Setup: uno-check --fix → wizard → run. Familiar MVVM, DI, HttpClient. In the slides below you can see how to install Uno Platform and configure your project. • Check Uno Platform here: https://lnkd.in/dPihsfzu • Check Uno Platform Studio here: https://lnkd.in/dnXPmUAu What would you build if you could design live and ship everywhere?

159

35 komentarzy

A while ago, I posted about a Performance Testing workshop I conducted. Back then, I didn’t get the chance to share the presentation itself. This is the previous post if you want to take a look 👇 https://lnkd.in/dTHe3Wd8 Now I’ve enhanced the presentation, and I’m happy to share it with you all 🤝 because I believe that knowledge grows when shared. In this workshop, I walked through: 🔹 Why performance testing is critical in real projects. 🔹 Performance Testing Types. 🔹 Key KPIs every tester should understand 🔹 Common Performance Bottlenecks. 🔹 Testing Process (PTLC) 🔹 Tools and approaches to get started 🔹 Frequently Asked Interview Questions. 🔹 JMeter GUI and CMD commands. 🔹 A Roadmap to dive more into Performance Testing. I know how challenging it can feel when you’re just starting, so I hope this presentation makes the path a little clearer. Resources that helped me prepare this workshop: 🔗 https://lnkd.in/dyXGWpYn 🔗 https://lnkd.in/dAd_BT-t 🔗 https://lnkd.in/dQM4zxJD 🔗 https://lnkd.in/diqpHJ9h Thanks to Mr.Raghav Pal and Mr.Rahul Shetty (Venkatesh) for facilitating these concepts 👏 💬 If you check it out and have any questions, feel free to reach out. I’ll be glad to help as much as I can. #SoftwareTesting #PerformanceTesting #KnowledgeSharing #TestingCommunity #LearningJourney #Workshop #Testing #PTLC #KPIs #Performance #Bottlenecks #Presentation

73

10 komentarzy

The Most Excited People About AI Coding Are Usually the Ones Who Can't Code And that should tell us something Walk into any tech conference and you'll see the pattern: Business people raving about "vibe coding" and natural language programming. Stakeholders convinced we're months away from replacing developers entirely. Meanwhile, the actual developers? Eye rolls and quiet skepticism. Here's why we're skeptical and why I think we're making a mistake. We know what "good" looks like. When stakeholders see AI generate a login form in 30 seconds, they see magic. We see security vulnerabilities and spaghetti code that'll break at scale. Our standards are higher. That's not a bug, it's our advantage. "I tried it 2 months ago; it's not there yet." I hear this constantly. But these tools evolve weekly, not yearly. When was the last time you actually experimented with the latest versions? Not a 5-minute test, but real exploration of what they can and can't do? The context problem is solvable. "Build me a login system" = garbage code "Build me a NextJS 14 login with TypeScript, JWT auth, following these API patterns..." = actually useful The difference isn't the tool; it's the prompt engineering. From Binary to Natural Language: 1940s: Machine code 1950s: Assembly 1990s: High-level languages 2020s: Natural language programming Each transition felt threatening. Each time, programmers adapted and became more productive. We're at the next evolutionary step, responding with the same fear. The advantage we don't realize: Yes, people are launching apps with vibe coding. Most crash immediately. But we can tell good code from bad code. We understand architecture, security, scalability. Instead of seeing AI as competition, see it as a junior dev that codes fast but needs experienced oversight. What I actually use AI for: • Prototyping small features (surprisingly good) • Writing boilerplate (saves hours) • Generating test cases (catches edge cases I miss) • Debugging (fresh perspective) Not replacing my coding; augmenting it. Result? 30% faster shipping while maintaining quality standards. The real opportunity: There's a massive knowledge gap between business hype and developer skepticism. Whoever figures out the practical middle ground first has a huge advantage. Here's what I'm encouraging you to do: Openly Share AI-assisted projects without the hype or hate. Discuss: • What actually works (and doesn't) • Prompt techniques for better code • How to review AI-generated code • Real collaboration examples Not to show off, but to let others learn. The future isn't human vs AI. It's informed humans with AI vs uninformed humans without it. Let's figure this out together instead of dismissing or overhyping it.

228

36 komentarzy

🤔 Do you want to know more about monorepos? 🤔 Wondering what their benefits and pitfalls are? Want to understand the tool landscape and the companies and business models behind them? Here is my newest article - "An Introduction to Frontend Monorepos" It is comprehensive and a 20 minute read, covering the benefits and pitfalls, and compares PNPM Workspaces, Nx, Turborepo, Bazel, Buck2. https://lnkd.in/d3yqWRWe #monorepo #nx #turborepo #pnpm

72

2 komentarze

🚀 Freelance vs Full-time Software Development in Germany - When to choose what In Germany's technology market, both freelance developers and permanent employees play important roles. The right choice depends on your business needs. ✅ Freelancers are the better choice when ⚡You need very specific expertise for a clearly defined project or technology stack ⚡Speed is important, since freelancers can usually start quickly without long hiring processes ⚡Your workload is project-based and does not justify a permanent hire ⚡You want flexibility to scale teams up or down without long-term obligations 👩‍💻 Permanent employees are the better choice when ⚡You want to build long-term product knowledge and strong company culture ⚡Continuity in core systems is essential ⚡The role requires deep integration with the business and its processes In short: 👉 Choose a freelancer for focus, speed, and flexibility 👉 Choose a permanent employee for stability, culture, and continuity The value lies in knowing which model fits your current challenge. #Freelance #SoftwareDevelopment #TechHiring #ITFreelance

38

How to Manage a Thriving Software Development Team Without Being On-Site: I manage my team remotely. Here’s how I do it: I used to think: Presence = Leadership. – I was in every call. – Answering every message. – Always involved. But that’s not leadership. That’s control. I learned: → You don’t need to be there. → You need systems. → You need trust. I made a shift: • Empowered my team. • Gave them responsibility. • Let them lead. • Stepped back. The result? ↳ Things got done. ↳ Deadlines were met. ↳ Problems solved without me. Now, my team thrives. Even when I’m not there. Are you leading? Or just managing? Let’s talk in the comments. Follow for more insights.

57

6 komentarzy

“We’ll cut your salary if you are 1 minute late to the office.” But the same office says at **6:59 PM**: “Can we have a quick call?” This isn’t about discipline it’s about mindset. Some organizations still equate productivity with presence, rather than impact with outcomes. A few points to reflect on: * Productivity is not measured by the number of hours you sit at a desk it’s about the value you create. * Deducting salaries for being “1 minute late” only builds fear, not performance. * Employees who feel respected and trusted often go above and beyond, without being asked. * If organizations expect flexibility beyond office hours, they must also offer flexibility in return. A healthy workplace = outcomes over clock-in time. Because at the end of the day, it’s not about when you log in it’s about what you deliver. Respect time. Respect people. Focus on results. #WorkCulture #EmployeeExperience #Leadership #Productivity #FutureOfWork #WorkplaceCulture #RespectAtWork #TrustAndTransparency #memes #funnymemes #officememes #corporatememes #memesdaily #dailymemes #justforfun

414

8 komentarzy

𝗛𝗼𝘄 𝘁𝗼 𝗶𝗻𝗰𝗿𝗲𝗮𝘀𝗲 𝘆𝗼𝘂𝗿 𝗰𝗵𝗮𝗻𝗰𝗲𝘀 𝗼𝗳 𝗴𝗲𝘁𝘁𝗶𝗻𝗴 𝗮 𝗽𝗼𝘀𝗶𝘁𝗶𝘃𝗲 𝗿𝗲𝘀𝘂𝗹𝘁 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂 𝗺𝗲𝘀𝘀𝗮𝗴𝗲 𝗮 𝗿𝗲𝗰𝗿𝘂𝗶𝘁𝗲𝗿 𝗼𝗻 𝗟𝗶𝗻𝗸𝗲𝗱𝗜𝗻? I often receive messages like this: "Hi Mariana, I’m a Senior Kotlin Developer with 10+ years of experience. Do you know of any open positions?" There is absolutely nothing wrong with reaching out. I appreciate when people take the initiative, and I try to reply to everyone. But let’s be honest. What are the odds that I am currently looking for someone with that exact profile? It is not impossible, but you would need a bit of luck. Here is my advice: Start by finding a position that matches your profile (in a formal published job or in a post shared on LinkedIn). Then contact the recruiter or talent team who posted it. The chances are much higher that the person you message is directly involved in that vacancy or knows who is. #JobSearchTips #RecruitmentAdvice #LinkedInTips

31

14 komentarzy