Gregory Meinke

No matter what language you’re programming in, errors happen. One great thing about #Rust is that you can diagnose and act on them quickly – if you know which tools and mechanisms to use. Learn more on our Tech Blog. https://bit.ly/4gmccX5

2

Best session about S3. Do not miss it!

3

Santana Row shopping center in San Jose has implemented a ticketless parking system that eliminates the need for drivers to take a ticket upon entry and pay at a pay station upon exit. Instead, drivers can simply scan a QR code (see photo) posted throughout the garage using their phones, enter their license plate number and credit card information on the website that pops up, and a camera will read their license plate and open the gate as they exit. While this system may seem convenient and efficient, I think there is a significant security concern! There is a risk that perpetrators could replace the posted QR code with their own, which would redirect drivers to a fake website where they would unknowingly enter their credit card information. This could lead to unauthorized charges and potential identity theft. It is crucial for the shopping center to address this security concern by taking appropriate measures to protect drivers' personal and financial information. They must ensure that the QR codes posted are authentic and that there are no vulnerabilities that could allow perpetrators to manipulate the system. As an alternative solution, pay stations could be installed for shoppers to use instead of relying on their own phones.

32

12 Comments

Grace Hopper was instrumental in the development of compilers and COBOL. Her famous quote, «The most dangerous phrase in the language is 'we've always done it this way,'» calls for challenging the status quo when addressing complex or wicked problems. Hopper's quote manifests that software engineering requires innovation and flexibility rather than sticking to conventional methods that can limit problem-solving. Software architects and engineers must question current practices to design scalable and resilient systems that remain relevant and adaptable as requirements and technology evolve. #softwareEngineering #softwareArchitecture #statusquo #problemSolving #innovation #flexibility #resiliency #scalability #adaptability

8

Super interesting (and technical) breakdown on how the folks at ClickHouse are transforming the simple, flexible JSON format into something that can be leveraged at hyperscale. An excellent example of how sometimes scale can make you do crazy things.

1

Shameless rip from Austin Parker’s BlueSky. But this whole thread is just too good! If you are passionate about #observability you’ll love this! Find the rest here! https://lnkd.in/gsvS_Jpz “”” 1. Metrics are good, actually, but most of you use them very poorly. … 4. there are no silver bullets when it comes to telemetry. you're trading between speed of access, data resolution, and retention … 5. you are not going to build a better datadog on-prem, they have a twelve year and twenty billion dollar head start … 18. the actual goal of observability is to have the data you need to find the answer rather than to have the data that contains the answer … 32. if you have thousands of dashboards, you have no useful ones … 44. single panes of glass are for glass cleaner, not o11y “””

34

3 Comments

Great article from Tom Krazit with some interesting takes “I care less about specific formats, I care more about what I can get out of it, the scalability needed to operate and the compatibility and integration with different tools," #data #datalakehouse #bigdata https://lnkd.in/geggTe4h

30

1 Comment

Excellent article. I agree with the two areas that continue to encounter the most resistance, Continuous Integration (meaning actually continuously integrating via trunk based development) and Whole Team collaboration. Whole Team methods continue to be challenged by the desire for high resource efficacy/utilization.

8

2 Comments

Practical explanation of API’s the next time you are in a buzzword salad meeting… https://lnkd.in/e-HSTwC3

3

A new Jepsen report from Kyle Kingsbury looking at the Kafka-compatible Buf: https://lnkd.in/gijxaHzr It includes broader findings about the Kafka protocol and implementation too: "We also characterize four issues related to Kafka more generally, including the lack of authoritative documentation for transaction semantics, a deadlock in the official Java client, and write loss, aborted read, and torn transactions caused by the lack of message ordering constraints in the Kafka transaction protocol. These issues affect Kafka, Bufstream, and (presumably) other Kafka-compatible systems, and remain unresolved."

40

1 Comment

Worth reading to quickly understand what's going on in the Redis universe.

1

Appreciate seeing that App Store review time has roughly halved since the summer (down to about 4hrs compared to 9hrs). I can't help but wonder why starting a review for Testflight external beta is still at the 8hr mark (though I certainly understand that those should be lower priority compared to production builds). I +1'd the Google Play IN_REVIEW status issue and recommend others do the same! On the green goblin [Android] side of things, I've personally experienced a lot of variance lately, resulting in some unexpectedly [days long] reviews. I also see that Google recommends waiting for production reviews while alpha reviews are in-progress, citing longer review times. My experience has been the opposite, where the synchronous reviews results in a MUCH longer review cycle. The numbers point to improvement, but there's still further progress to be made, both for timing and consistency of policy enforcement.

9

1 Comment

When is it good to understand the purpose of a fence (rule, tradition, or practice) before removing or changing it? https://lnkd.in/gY3xGmwh https://lnkd.in/gbxjJKJ6 Chris Lucian #MobProgramming

4

2 Comments

Yes, our engineering team really did run CockroachDB on spot instances. I can explain. Our customers are running mission-critical workloads across clusters with hundreds of nodes, and it is paramount that our engineering team can test at a similar scale. But testing at this scale can get expensive. We need to be able to meet our customers where they are, but we also need to be able to control our costs as an organization. Spot instances can create significant savings over VMs, with savings of up to 90% a year. What if we could run long-running clusters on them? Besides saving money we would be able to leverage the unpredictable nature of Spot Instances for some exciting chaos testing! The effort to keep CockroachDB available and workloads predictable while nodes are rapidly disappearing would help us harden CockroachDB. Adam Storm's blog captures our entire journey, diving into the methodologies we chose, lessons learned, and yes—even the impact of preemptions. At Cockroach Labs, our engineering culture doesn't just push the boundaries of what's possible with a mission-critical database; it fuels technical innovation across the board. The results are fascinating, so give it a read if you're curious about running a distributed database on spot instances! Special thanks to Bilal Akhtar, Herko Lategan, David Taylor BabuSrithar M, Sambhav Jain, Shailendra Patel, Vidit Bhat, and Bhaskar Bora https://lnkd.in/et-aEjxm

78

4 Comments

The Capital One Tech blog is full of useful tips to help make you and your work more efficient. Today’s tip: Consider using these design patterns in your next microservices app and make organization more manageable >> https://dy.si/FUWLJ

1

The final deep dive on change query support in the table formats is ready. This one covers Apache Paimon, focusing on understanding the change query support through the lens of its internals. https://lnkd.in/dFfM_8nA

28

Datavolo just released an #ApacheNiFi Flow Diff GitHub Action to help with branching & Pull Requests when making changes on your NiFi flows! Here is a demo and the link to the marketplace is in the first comment.

52

4 Comments

"Build in primitives" -Andy Jassy, #Amazon CEO https://lnkd.in/gHMYt7NX Happen to take the time to read this year's Annual investor letter from Andy Jassy. Deep in 2nd half, it talks about how Amazon started thinking about "building in primitives" and how it has been game-changing for them and their customers. Probably old news for some, but eye-opening for me. Definitely a good read!

2

Why does someone (me), with a long career in technology, spend so little time writing about it? I've been asked that more than once, but only stopped to think about how to answer it this week. It turns out I do write about technology, and leadership applied to technology - it's just that I'm not as obvious as some might expect/demand/require. What are you doing in your life that is more than what it seems? And if you see it for what it can be, does that fill you with joy? If you want my perspective you can read it in my Substack! #stoicism #tech #leadership

12