Oz Katz

Thrilled to enable 💪 Bedrock - llama 3.2 cross region inferencing - https://lnkd.in/dad-phUS s/o Steffen Ridderbusch (+4 more updates 👇) 💸 Azure AI rerank endpoint cost tracking s/o Emerson Gomes 🛠️ Logging - response redaction on `turn_off_message_logging` s/o Ilari Scheinin 🔨 Cohere - support cost override for cohere rerank models s/o Jerome Roussin ⚡️ Proxy - fix returned headers 

8

New blog post: "Subtitle Shenanigans in SwiftUI’s Menu" SwiftUI’s Menu component is a delightfully powerful API in terms of the complexity of the interactions it supports compared to the API footprint, but if you need to use subtitles then things can go a bit off the rails. Let’s dive in to Menu use cases to get a better understanding of its sometimes odd behavior: https://lnkd.in/d-Pm4kMB

6

2 Comments

I've had the privilege to know Max Kanat-Alexander for the last year through our Hangar DX community, and since then I've learned so much about DevEx him. Max is the author of Code Simplicity, was a TL at Google who defined the code review guidelines and was also the Chief architect of the Bugzilla project. I recently chatted with him about the Developer Productivity and Happiness framework that LinkedIn published last year. There are so many nuggets in that podcast that we may have to do a volume 2. Listen to the full episode on YT, Spotify or Apple podcasts: https://lnkd.in/dtAwVgBy Some takeaways: - There cannot be developer productivity without developer happiness - Iteration time and context switching are key concepts that impact developer productivity. - Understanding and catering to different personas of developers is crucial for effective developer productivity efforts. - It's significantly more important to understand what to measure than how to measure it. Most teams fall into the trap of measuring the wrong metrics. #developerproductivity #developerhappiness Checkout the Hangar DX community at https://dx.community We are hosting a Zoom session with William Howell from Okta this Thursday at 11am PDT!

15

📢Let’s take a look at one of the most impressive P0 companies, MongoDB🚀 Founded by Eliot Horowitz, Kevin Ryan, and Dwight Merriman, and led by Dev Ittycheria, is experiencing impressive growth, with a 22% year-over-year revenue increase. This growth isn’t just about the strength of their product; it’s a testament to their deep integration as a Priority 0 (P0) company within the engineering systems of countless organizations. However, they didn’t start out this way. The company started in hopes of building a scalable app engine, before realizing that the complementing database they were building is what their customers really wanted. From there, the company started to take off. Beyond serving as a core database, MongoDB has helped consolidate the database stack without sacrificing quality. A standout in their offerings is Atlas: a fully managed, cloud-based database service that enables organizations to deploy, operate, and scale MongoDB databases across various cloud providers. Atlas doesn’t just stop at databases; it extends into other critical areas like vector search, time series, and more. MongoDB’s focus on unstructured data positions them perfectly for the AI-driven future. Their ability to support multiple data use cases on the same dataset is incredibly powerful, enabling companies to reduce the need for multiple copies of data. For example, their search product allows you to index your data for search use cases directly on top of the existing dataset—a game-changer for many businesses. As long as MongoDB continues to innovate, develop new features, and support emerging tools while improving performance (MongoDB v8.0 has brought significant enhancements), they’ll remain one of the go-to choices for companies willing to invest in robust, future-proof technology. This isn’t a debate about SQL vs. NoSQL. It’s about recognizing that a strong P0 companies are made through consolidations and strategic pivots along the way. Most data and engineering leaders I know could not imagine their world without MongoDB or begin to think about replacing it. And that tells me everything I need to know about P0 companies.    What’s your take on the consolidation strategy MongoDB is leading with offerings like DocumentDB, time series, search, vector search, query APIs, and more?  #MongoDB #TechInnovation #P0 #DataDriven #AI #CloudComputing

44

1 Comment

🔧 Tactical CTO vs. 🚀 Strategic CTO: Which one are you? Some CTOs are deep in the technical trenches every single day, while others think years ahead. One solves today's problems, while the other focuses on building for the future. It's not just about the job title but how you approach the role. I've been thinking a lot about the differences between Tactical and Strategic CTOs and how each brings something crucial to their companies. There's a balance between managing what's in front of you and planning for what'll come next. Here's my take: Most of the time, CTOs must start as 90% tactical / 10% strategic and eventually transition to the other side of the spectrum. If you're a new CTO, you should first learn about the difference between being tactical or strategic, internalize if you can be either/both, and then, if you decide to embark on this journey, figure out at what stage your company is at, and focus on your impact based on it. --- Note: If you have been successful in the past and have connections and resources to launch a new venture, then this only partially applies to you. --- At the earliest stages of a tech startup, you'd want to be the tactical CTO side who's hands-on, building the technology that will one day generate the revenue necessary to create a real business. Your focus should be on producing stuff as quickly as possible and iterating on the feedback you gathered from your customers using your products and features. At this stage, you should know how every single line of code in your codebase works. Eventually, the time comes when you'll need to start bringing fantastic talent to your team. Your time splits between sourcing, hiring, onboarding, and building. At this stage, as the team grows, you will need to become more strategic (and less tactical). I've met MANY CTOs struggling in this phase (including my younger self), and I usually tell them they need to have an internal dialogue to discover if their true calling is being a CTO or staying more in the tactical realm of things as senior ICs. Finally, if your company is successful enough and you haven't run out of money, there always comes a time when your team mostly rewrote every line of code you've contributed. You are now spending almost 100% of your time on the strategic side of things, planning for the long term and having mainly high-level discussions with your team, among many other responsibilities. I could go way deeper into defining each type of CTO. I'll gladly do it in a future post if this one generates enough interest. Do you agree? - Hit me up if you or your CTO are struggling with this transition, and I'll be happy to help.

25

4 Comments