Aaron Parecki

Not all #IBMMQ events are equal, some you'd probably like to hold onto for longer than others. Learn how #MQEV allows you to do this and choose how long to keep the events you have captured based on any criteria you need. #WorkSmartWithMQ

5

The best kind of hacking projects are the ones you care about breaking. At Viam, we ask our engineers to spend 20% of their time working on side projects. The projects that are the most impactful are the things that people care about if they break. I want engineers to look for things in their personal life that they want to fix or make smarter rather than a flashy, but mostly useless, gadget. These projects don’t have to be big or expensive to make an impact either. There is already simple software out there that can be a massive problem solver. If you look at my own hacking projects, they are all things that impact my daily life. For example if my cat food feeder breaks, my cat gets hungry (and mad), if my sprinkler system that runs on Viam breaks, my lawn dies, etc. etc. All of this is to say that by using your time to fix real world problems you inspire others to do the same, and open up a world of opportunity. What device in your life came to mind while reading this? What is holding you back from making it smarter?

71

4 Comments

How to knock veteran programmers down a peg. Test them on this: What if a meeting scheduled on the exact minute a leap second is added needs to be rescheduled to the next available "normal" minute? Tests that asses someones skill as a human compiler or quiz them about obscure language features are a poor way to find out whether they can actually deliver value to a company.

3

I had a great time diving into the technical weeds of design system engineering on the Syntax.fm podcast with Wes Bos and Scott Tolinski. We cover a lot of ground here! https://lnkd.in/eJjnNZZ6 “What’s in a design system figma library isn’t as much of a spec for developers to build it out. What this figma library is a promise of what is in code. It is a representation of what exists in the coded design system.” #designsystems #frontend #ui #design #development

148

5 Comments

What do we do best? Lynne Doherty, Sonar's President of Field Operations, sums it up pretty well: code quality and security, whether human-written or AI-generated. Check out her open letter on our company blog to learn a bit about her and the journey ahead for Sonar, and how we’re dedicated to helping developers and organizations solve the trillion-dollar challenge of bad code.  #CleanCode #CleanasYouCode #codequality #devops #developertools #genAI #AI #codesecurity

7

1 Comment

I feel like modern devrel is a result of drift, not intention. As a result, devrel tends to work pretty poorly — but NOT because devrel itself is bad! I unleashed my hot devrel takes with Brian Douglas (love that guy) at East Glisan Pizza Lounge (love that pizza). Watch on the OpenSauced YouTube: https://lnkd.in/g_ms3EAD #developerrelations #devrel #growthmarketing #productmarketing #productledgrowth #plg #devtools

38

3 Comments

This demo is so awesome in so many ways -- kudos to Caleb Olson for developing the Poopcopter https://lnkd.in/dxVshnUW

2

2 Comments

It was hard, but we now have a primitive at Gadget that lets us do absolutely 0 downtime atomic changes to an application's structure or data under the hood, with 0 requests dropped. I call it "request catching" but it was inspired by this Braintree eng post I read long ago For stateless workloads like serverless functions, 0-downtime deploys are pretty easy. You stand up the new one next to the old one, use a load balancer to start sending requests to the new one, and slowly stop sending requests to the old one. But for stateful workloads, it's much harder. You can't just start a new Postgres and send some queries to the new one and some to the old one without lying to somebody about state. If you want to be consistent, there has to be one source of truth. Fancy DBs have quorums for this, but PG doesn't. If you want to be consistent, you're effectively forced to have some tiny-but-real window of downtime in between draining the old one and starting the new one. That said, there's nothing forcing you to return errors to clients while that is happening. If your infrastructure supports it, you can pause requests while this changeover is happening under the hood, and then resume them once it is over. Clients will notice a longer request that normal, but it will be served like normal and they'll be none the wiser! What's required to do this though is a deep deep integration between the load balancing infrastructure and the thing doing the database deploy under the hood. We've built this up using a distributed locking tool, where all requests start by taking out a shared lock. When we're ready to do the maintenance under the hood, the maintenance workflow takes out an exclusive lock, blocking all requests from proceeding. The workflow does the atomic change it needs to make knowing it has exclusive access which means nothing will change under its feet, and then releases the exclusive lock as fast as it can so those requests can proceed. As an optimization, we only check the lock on the request path if an app is marked as near a maintenance window. This is only possible because of Gadget's architecture where we bundle together the load balancer, the request processing layer, and the database access tier such that we can reliably intercept all requests and all database transactions and do this lock checking. Its these nasty, in-the-weeds details that make me so proud of Gadget -- we can do world-class engineering stuff under the hood on behalf of all our apps without them ever noticing. If you're interested in doing this on your stack some OSS tools have the primitives you need! We use nginx for our load balancer, Temporal for the reliable workflow execution and we're currently using postgres advisory locks for hte locking. I think the Braintree post has been lost to time after they got acquired, but @simonw has a great post on the subject here: https://lnkd.in/eZmiktGT

51

A general request for fans of Two Voice Devs or developers that follow me. Mark Tucker and I love doing the show - but we're keenly aware that there is *SO MUCH* that has been going on, that we're missing stuff. We love having guest hosts on, and right now, we're looking for guest hosts that can talk about two things in particular from a developer POV: * AI announcements from MS Build * AI announcements from Apple's WWDC We know there are lots of other AI stuff that happened at both, but we focus on developers - what can developers now do with these platforms that we couldn't before. We also try to stay away from employees of the companies themselves - we want people who have their own perspectives. Do you know someone? Do you know someone who might know someone? Are you that someone? If so - message Mark or me and let's find a time to chat. Image by Imagen 2 with the prompt: Greek wall art of a person exploring a cave with a candle in a lamp

8

Topics in #CopilotStudio are the core building blocks of a copilot which define how a conversation dialog plays out. Think of topics as a way to build out every possible conversation path that your copilot may have which will then allow your users to have a conversation that feels natural and flows appropriately. 📌 In the latest episode of our Building with Copilot Studio series, I walk you through the following: 1. The difference between Custom and System topics 2. How to create a topic with natural language 3. How to edit a topic with a combination of Copilot and manual methods 4. How to use question, message, and conditional nodes in topics 5. How to use entities and variables 🖥 Watch the full length video on YouTube: https://lnkd.in/d54kEeTY 📖 Learn more on how to create and edit topics with Copilot: https://aka.ms/mcs/topics 📽 Don't forget to subscribe to the Microsoft Power Platform YouTube channel to receive a notification of the next episode of our AI in Action: Building with Copilot Studio series: https://lnkd.in/dHmpZfSv #Microsoft #PowerPlatform #AI

25

1 Comment

T minus 4 hours to our first launch week event. Advanced mapping is coming to Flatfile. Making complex rules feel simple isn't easy. Come see how we did it at 10AM PT https://lnkd.in/es5v4uEm

33

1 Comment

Another day, another new, faster #LLM. Meet Claude 3.5 Sonnet from #Anthropic. "Claude 3.5 Sonnet operates at twice the speed of Claude 3 Opus. This performance boost, combined with cost-effective pricing, makes Claude 3.5 Sonnet ideal for complex tasks such as context-sensitive customer support and orchestrating multi-step workflows." https://lnkd.in/ecXUMhKE #AI #genAI #CX #AIorchestration

7

I'll be speaking at GOTO Chicago on performance techniques in Jepsen. It's gonna be a weird collage of parallelism, pure functions, immutable data structures, and deforestation with low-level techniques like bitsets, avoiding sharing between threads, packing structures into mutable arrays, dynamic compilation of primitive boxes, and macro iteration magic. October 21 & 22nd. https://lnkd.in/d3yedtc6

26

I'm finding some big flaws with SBIRs based on my morning reading today. I'm calling these out so we can collectively move faster... TIME is what I HATE TO SEE WASTED. (DoD SBIR/STTR Program Office--I know you're working hard! Please know the following is posted with respect and commitment to helping us all improve.) I just read through the Solicitation and Component Instructions for some of the pre-release topics that came out on the Defense SBIR/STTR Innovation Portal 👇 . Here are my observations: 1) One of the topics lends itself to COTS tools that are ALREADY AVAILABLE. Before DOD puts out a SBIR, is it researching existing tools or patents to make sure they don't make an award for something that ALREADY EXISTS? In lieu of going through the process of awarding a 6 month, $180k SBIR Phase I to multiple companies, could you ask existing technology companies to submit proposals for what they could deliver for $160k (art of the possible!)? 2) At least for the Air Force Broad Agency Announcement (BAA), MAJORITY VC- or PE-OWNED SMALL BUSINESSES are INELIGIBLE TO BID. From a past life, I thought this barrier to entry was fixed? This prevents DOD from benefitting from VC and PE dollars long-term. 3) The SBIR Phase I Cost Volume forces companies into a cost breakdown of materials, parts, supplies, labor, etc. and the Solicitation Instructions even specify that, "To reduce risk to the small business...companies interested in pursuing Phase II SBIRs... [should] have an adequate accounting system per General Accepted Accounting Principles (GAAP)... [which] WILL BE AUDITED by the Defense Contract Audit Agency." This PREVENTS the GOVERNMENT from being able to buy future commercial items from the supplier at scale and at a lower unit cost long-term. It also corrals the small business into expensive, counter-productive accounting practices Tell me what I'm missing here. Copying folks who may have opinions. Guy Filippelli Kevin Landtroop Jane Lee Robert Smith Ryan Connell

42

30 Comments

One thing I like about formally modeling systems in TLA+ and Fizzbee is that when someone asks me why a particular check is performed or a constraint exists I can show what happens when I disable it. Showing a counterexample that someone would never have considered is really fun. In fact, once you've developed a model, it's fun to start disabling stuff, just to see the impact. It really helps to internalize how each piece of the design contributes to the advertised properties. I did this yesterday with my Apache Iceberg spec after being asked about a particular data conflict case, more just for me to remind myself of what bad scenarios the conflict check in question prevented. I disabled it and got a counterexample of an undelete. Then I disabled delete operations and got a lost update from two conflicting updates.

49

8 Comments

Balancing the traveller experience with an Airport's cost to serve is what we obsess about at Beonic, we use advanced AI to turn IoT sensor data into people movement, queue time and occupancy before adding Flight Information, weather and historical models to make predictions Airport Operators can rely upon for decision making. Beonic's real time visualisations and multi-platform notifications help Operations teams balance great traveller experiences with the lowest cost to serve. This research really brings this to life; when we combine occupancy data, predictive models and weather data to determine how often public restrooms should get cleaned, the traveller experience improves significantly. https://lnkd.in/gkjSzCPj In the last hour of a long haul flight many travellers avoid the toilets with good reason, opting instead for a quick pit stop post disembarkation, our tech ensures those toilets close to your gate were just cleaned given the first impression of an airport shouldn't be formed on the back of a dirty restroom!

21

2 Comments

🎉 Breaking News: Swiizio is coming soon to Yocto! (Well… hopefully 😅) 🍓💻 Over the past few days, I’ve embarked on a wild mission: getting Swiizio to run on **Yocto Kirkstone** with **Qt 6.6** for the **Raspberry Pi 4**. 🚀  👉 Step one: wrestling with **Ubuntu 24.04** and its overly protective file permissions. The result? I had to negotiate with my terminal like a diplomat.   👉 Then came the hunt for a **Qt version** that’s complete enough, yet not too different, so I could avoid refactoring a codebase that, spoiler alert, has just surpassed **100,000 lines**! Yes, **100k lines**, and counting. 😅  By the way, does anyone know of a **keyboard brand with reinforced keys**? I might need one for the next **100,000 lines of code**... 😂  On a serious note, progress is happening, and I hope to announce soon that Swiizio is proudly running on Yocto. 🙌  If you’ve got any tips, insights on Qt or Yocto, or just a little moral support, I’m all ears! 🙏  #Yocto #Qt #EmbeddedLinux #RaspberryPi #LinuxEmbedded #100kLines #KeyboardSOS   #OpenSource #DevelopersLife #EmbeddedSystems #Linux #SoftwareDevelopment #DevLife   #CodingChallenges #TechCommunity #IoT #CrossCompilation #Buildroot #OpenWrt #PetaLinux   #WindRiver #SoftwareEngineering #Qt6 #YoctoKirkstone #EmbeddedEngineering #DevHumor   #RaspberryPi4 #LinuxKernel #TechLife #EmbeddedSoftware #DeveloperTools #OpenEmbedded   #ProgrammingLife #LinuxDevelopers #EmbeddedWorld #DevMemes #SoftwareTesting #IoTDevelopment   #SoftwareOptimizations #SysAdminLife #TechInnovation #QtFramework #LinuxCommunity  

1