Sarto J.

Trying to muddle your way through a poorly designed system architecture document is no fun at all. So in this guide, Ifeoma teaches you how to create helpful system architecture documentation. She talks about diagrams, making tech language accessible, communicating clearly, keeping things simple, and more. https://lnkd.in/gr54nX_U

275

Big news from the Auth0 crew 🎉 We just shipped six Developer Experience Principles to make auth feel invisible while you build. Think: Simple, Clear, Composable, Consistent, Quick, Magical. They��ll steer every doc, API, and UI choice we make—so you spend less time wiring login and more time shipping features. Catch the details from Micheal Lopez (VP, Design & Research) and tell us what you’d improve 👉 https://lnkd.in/eGVZRybz 

87

1 Comment

Developers love solving problems But we also love creating complexity we don’t need. If you’ve ever spent 30 minutes naming a variable, or built a folder structure worthy of a Fortune 500 startup for a project still in draft mode… You’re not alone. It’s one of the most universal developer habits. This carousel breaks down the five places where devs consistently overcomplicate things and the mindset shift that keeps your code clean, scalable, and sane. 👉 Which one of these do YOU overcomplicate the most? Be honest, we’re all guilty. #W3Schools #Coding #CleanCode #WebDevelopment #ProgrammingTips #Developers #SoftwareEngineering

462

36 Comments

I love this take on the “10x engineer” phenomenon. Ubuntu (the African concept, not the OS) strikes again. “I am because you are”… “Individual engineers don’t own software; engineering teams own software. It doesn’t matter how fast an individual engineer can write software. What matters is how fast the team can collectively write, test, review, ship, maintain, refactor, extend, architect, and revise the software that they own.” https://lnkd.in/g725SPDb

40

The era of building an Internal Developer Platform (IDP) from scratch is dead. The DIY approach is too complex and unsustainable. The Platform Engineer's role is shifting from Plumbing to Product Ownership: - Stop Wiring: End the cycle of maintaining fragile, custom integrations and tooling. - Start Curating: Adopt commercial or open-source IDPs (like OpenChoreo) that solve the hard, common problems. - Focus on DX & Value: Dedicate time to designing Golden Paths and governance that accelerate developer velocity and map directly to business outcomes. Learn more → https://lnkd.in/gvKdf383 Meet the author Lakmal Warusawithana at KubeCon booth #1243 to see how OpenChoreo is redefining platform engineering."

30

The past few weeks have been a lot of work. We’re getting close to releasing the app and the goal is this weekend. Most of my time has gone into final polishing and fixing issues based on tester feedback. We planned to release last week but the new macOS 26 and Xcode 26 created migration issues that took longer than expected to sort out. Outside of that I’ve been spending most nights improving my CAD skills. On the eye tracker side we finalized two designs. One is a full frame model and the other is a portable tracker that can fit onto any frame. This gives us flexibility depending on how people want to use it. We’ve also been experimenting with event based cameras for eye tracking. These are very different from regular cameras. They can run at extremely high frame rates and we are testing whether they can capture microsaccadic activity. If this works it will give us a much more detailed view of eye movement. In parallel we added a heart rate sensor and a few other sensors to the glasses. The idea is to keep expanding what the system can measure and see how the different signals can work together. There’s still a lot to figure out but things are moving forward and I’ll share more once the app is live and we have more results from the hardware experiments.

16

Blocking shared mailboxes one by one? Ugh, that’s a task I don't enjoy! But it’s something we can't ignore. Allowing direct sign-in to shared mailboxes opens doors to impersonation and goes against their very purpose. The same goes for resource mailboxes like room and equipment mailboxes. So, blocking sign-ins is the way to go! But doing it manually? That’s a nightmare. However, a few lines of code can save a whole lot of effort. With just one script, you can: ✅ Export the sign-in status of shared mailboxes ✅ Block sign-in for shared mailboxes ✅ Identify the account status of room and equipment mailboxes ✅ Disable sign-in for room and equipment mailboxes One single PowerShell script to control all your mailboxes sign-in! You can download the script from here: https://lnkd.in/gZgW9w6r #ExchangeOnline #SharedMailboxes #powershell #powershellscripting

41

1 Comment

👀 Think accessibility means adding aria-label everywhere? Think again. We’ve got good news: accessibility is built into the web. Literally. Native HTML does so much more than most devs give it credit for. But somewhere along the way, we started reaching for libraries and ARIA roles to fix problems that... didn’t exist in the first place. 🔍 Modals? Use <dialog>. 📂 Accordions? <details> has your back. 🎛️ Dropdowns? <select> is your friend. Want to know when to use ARIA? (Hint: almost never.) Curious how accessibility ties into the European Accessibility Act? Or just want to stop fighting your code and start shipping inclusive features faster? 🧠 Read the post and discover why native HTML is your best ally 👉 Link in the first comment. #HTMLFirst #Accessibility #WebDev #a11y #InclusiveDesign #ustwo

18

4 Comments

⚖️ Important doc about what actually makes your apps bigger...and how to optimize them. When examining the resulting artifact of a release build for an app, it's common for developers who are unfamiliar with native Android and iOS development to be surprised by the file size — it's usually much larger than they would expect for an app if they were to download it from an app store. This is not the actual size of the app that will be distributed on app stores! When people talk about app sizes, they mean the size of the app that they will download to their device, not the size that will be uploaded to app stores or shared in development and testing. Check out the doc to learn more about the nuance of forecasting (and optimzing) app size: https://lnkd.in/g2dJ7ciM

53

1 Comment

Last night I vibe-coded a Gemini 2.5 Tumbler for developers who’d rather not pay for AI or be watched while doing it. I realized I had about a dozen Google accounts, each with access to the free Gemini API. So I thought, what if I could cycle through those keys to bypass the two-requests-per-minute limit? Next I thought, what if I could make this part of an anonymous network where users could anonymously contribute their api keys. That was the spark. A tumbler is a system that mixes and obscures data to break the link between source and destination. The Gemini Tumbler applies that concept to AI inference by scrambling identity, content, and request paths to keep usage private. If you’re researching a sensitive topic or working on something that shouldn’t be traceable, this obscures who made what request and when using a chunked request patterns. Each request is segmented and separated. It’s a privacy-first, zero-cost system that routes and anonymizes requests across multiple Gemini API keys and globally distributed edge-based serverless functions. The stack includes automatic rate-limit detection that dynamically reassigns requests to balance load and stay within key limits. At its core is a daisy-chained architecture using Supabase Edge Functions, Vercel and Cloudflare Workers. Each function operates independently: one sanitizes input, another hashes identity with rotating salts, another handles content. No single function has the full picture or any question. IPs, headers, and origins are wiped or randomized between hops. Best of all, no costly or slow blockchain required. It’s OpenAI-compatible. Just swap the endpoint and your app keeps running, now with the free Gemini Ai services and full anonymity. Ideal for political, journalistic, or privacy-sensitive use, it provides free access with strong obfuscation. Built for developers who’d rather not pay or be watched. https://lnkd.in/gEe_N4ZE

126

61 Comments

Technical product documentation is a full-time responsibility that requires a dedicated team of writers who understand technical concepts and technical practitioners. It’s not a part-time job you give to developer advocates to do between conferences. Developer advocates should absolutely contribute. They should consult. But they should not be accountable or responsible for the health of technical documentation. Documentation is part of the product. It’s part of the user interface.

132

10 Comments