Daniel Saltz

It's Sunday again, so let's implement more of Berkeley DB. Hope to finish the Rust implementation today and get started on another language... or another database? Come and see at 3:30PM CDT: https://lnkd.in/gzEjKQxw In your timezone: https://lnkd.in/ejJjk-xy #RustLang #Database

New 4149 update just dropped to help with the summer heat! tldr; your 4149 AI teammates are even smarter and more helpful with the proactive tasks they take on to support your team! Highlights include: + Improved momentum engine + Agenda view showing all the proactive tasks for the week. + Notion DB support so your 4149 teammate can check your task tracker, funnels, etc + More awesome blueprints + Tons of bug fixes You can see the full update here: https://lnkd.in/eG9XhVFr #ai #startups #product

31

3 Comments

🌶🌶🌶 Hot take… Old problem: if we put more devs on the project, we can deliver it sooner. Same thinking, new manifestation: we can hire more overseas devs for less total money to produce the same result as our US staff. Flaw in that thinking: product development is not an assembly line. Devs are not “interchangeable”. Software is as much an art as it is science. It’s a team sport. The people on your team matters. #tech #staffing #management #hiring #jobs #layoffs #software #startup #teamleadership

25

6 Comments

I never wrote a single line of open-source code until I started at Taranis. It's crazy how much startups depend on open-source products, but how little they usually give to the community back. Here's our story: Our open-source person is Avi Klaiman, our chief architect. One of those guys who'll code during the nights for the fun of it :) He created some very successful libraries by himself (react-leaflet-google-layer for example, with 10K+ weekly downloads), and for years wanted to push it forward in Taranis. A couple of years ago I took part in creating one (you can search for 'react-native compare slider'), but it was quite small. Recently, we decided to get serious, and opened a public medium page and GitHub account for our company! So far, we have published 3 articles: 1. Itai Goldman, our DevOps wizard, about using ArgoCD to deploy dynamic objects: https://lnkd.in/dmJYJt6A     2. Dan Erez, our internal AI entrepreneur about Data Cleaning for AI: https://lnkd.in/dT8fP38g     3. and Avi Klaiman about monitoring async Python GRPC services: https://lnkd.in/dng-YhmR Everyone is familiar with the 80/20 rule, but I think for the open-source world it's more of a 99/1. 1% of people spend their time on libraries and articles that 99% of others use. It doesn't have to be a huge project, it can be even a small article that'll make someone's life easier :) Any tips from your company on how to give back to the community?

28

10 Comments

A good short practical list!

3

When it comes to multiplayer games, many teams do the mistake of asking for "late validation" instead of "guidance early on". The bravest ones want to make their own netcode, and spend months doing one that only 3 people know how to maintain. (just don't) Others implement the entire game only to realize 6 months later that things don't work as expected (laggy movement, players not hitting what they shoot at). All of them think they're making progress. They feel like they can do it on their own. For them, multiplayer doesn't sound like a big deal. There are other problems that are higher on the priority list. But reality is different: they simply don't realize what's coming. So when they release and their infrastructure blows up, cheaters appear to ruin the fun, and players leave negative reviews, it hits hard. At that point, proper multiplayer suddenly becomes a priority! But the damage is done, and the deadline to do a super job gets super-tight. Was it worth to wait for "late validation"? It would have been easier to get help early on to pick the right tech stack, netcode framework, and system architecture. Because no matter how good you think your multiplayer game is: If it lags, it sucks. Fixing it early on might cost you 2K$. Fixing it close to / post release will cost you your project. >>>>>>>>>>>>>>>>>>>>>> P.S: I post about Multiplayer Game Development 5x/week. Follow me for more insights, or book a call to supercharge your multiplayer game!🔔 #JustDevIt #gamedevelopment #multiplayer #netcode #gamedev

6

The best is the enemy of the good It is a Russian saying that basically means that sometimes, when something's done well, trying to make it perfect doesn't add much value. There's also the 80/20 rule: 20% of effort brings 80% of the result. Both of these ideas point to the concept of Good Enough Solutions: they might not be perfect, but they get the job done and deliver value to customers. For Senior+ Engineers, knowing when to stop tweaking and accept a good solution can save a lot of time and money for a company. It's not about settling for mediocrity, but rather being smart about where to focus efforts. While we all want to aim for the best, recognizing when good is good enough helps us move faster, achieve results sooner, and adapt more quickly. 🤩 #mondaynotes #sdexperience #agile

9

TL;DR - Want a ticket to Reactnext/ Node.tlv? We'll get you there! Full-stack engineering means different things to different companies. Very few people really do specializes on both sides, so why call it Full-stack? is it just a pretentious hype? What does it really mean? And why do we keep using it? At Riverside, being Fullstack is about increased perspective, reducing limitations and having a ton of ownership. ✅ It means being able to move quicker, as you have less dependencies. ✅ It means you have the knowledge to choose the right tools to solve each problem. ✅ It gives you flexibility to navigate special requests or features that require both front and backend. ✅ It means you're a true expert on one domain, but have more tools in your toolbox for special cases than just one language. Being well rounded is very important to us, and that's why I am very excited to sponsor both ReactNext Conference and Node.TLV this year. This is truly a Fullstack sponsorship! 😎 ⭐ aaand we have the opportunity to give away one free ticket ⭐ to one conference! So what's your passion? which side do you lean into more? Or maybe it's the other side you want to invest in? Let us help you with that! Write in the comments which conference you prefer out of the two and the comment with most likes by 24.5 will get a free ticket to your conference of choice from us!

31

11 Comments

Excited about Excalibur.js ECS? Matt Jennings has written an excellent new post about System-less Components. Lots of goodies: like how to build one-way platforms, and platforms that can carry players with components! https://lnkd.in/eG6h-NAG #excaliburjs #gamedev #typescript #javascript

4

1 Comment

Three things everyone knows about #MVP: 1. It's Minimal 2. It's Viable 3. It's a Product Three things often misunderstood about MVP (starting with the second bullet): 2. It should work outside your lab, without ridiculous hand-holding on your part. Onboarding is fine and is a good way to get feedback and create a long-lasting relationship with your customer. 3. It solves a REAL problem for a REAL user. 1. The one most #ProductManagers miss: Minimal ≠ Small. Think about the MVP for a spaceship 🚀 . It's an extremely big and complex project, even for the MVP. The same applies to many simpler products. 🎊 The good news is, there are frameworks to help you scope your MVP and reduce redundant features while still solving the main problem. 🎊 🎊 🎊 The REALLY good news is #Iteraite has augmented those frameworks with #AI to make your process even better and faster. Signup for our new applet here: https://lnkd.in/evCaEZik #ProductDevelopment #ProductManagement #GenAI

10

Here's how tech agency founders kill their LinkedIn engagement: “We at Acme Software build software. If you need software, let me know.” Why would I engage with that? There’s no story. There’s no transformation. Nothing to personally connect with. Do this instead… Write posts with these 10 free prompts to connect with your potential customer: 🔹 What it’s like to work with your agency - your process 🔹 How your personal values have influenced your client experience 🔹 Short case study of a client (used with permission) 🔹 What it’s like to work for you - your people and culture 🔹 5 things people don’t know about your industry (and why it matters) 🔹 The story of why you’re in the tech consulting business 🔹 How you developed the product or service you’re offering 🔹 What experience led to the original idea? 🔹 Props for your team that you got from a client 🔹 A time when you turned a client’s opinion about consulting around Make it 200-250 words (this post is 239 words). Make it personal. Make it double-spaced. Make the sentences short. And post it as the owner or partner, not on your company page. This will: • personalize your brand • build trust with potential clients • demonstrate your expertise (built from experience) • give prospects a "hey, we're like that client" connection moment When you post it, shoot me the link. I'm ready to kickoff the engagement! ------------------------------- I'm Jason and I write human-powered content to help tech agency founders. Message me if you run a tech agency and are trying to get going on LinkedIn.

11

3 Comments

The dumbest part of the whole post: "The best part? He spent $0 in paid marketing." Most of this is just fluff in order to drive signups to this guy's "strategy nerds" newsletter...and it works. While this guerilla marketing framework is indeed reproducible for many businesses and entrepreneurs, don't expect the same level of results and certainly don't expect it in the same amount of time (4 months). Most startups and small businesses have tighter capital restrictions and smaller teams to execute on this to achieve the same level of results. Maybe it's true Gas spent $0 on paid ads, but the whole guerilla marketing operation didn't cost $0. Keep in mind, this founder is flush with capital after a $100M acquisition from Facebook. With that amount of money, he can then hire a team of developers to build Gas and a team of guerilla and social media marketers to execute on the strategy. All of that costs A LOT OF MONEY. So maybe it's true he didn't spend money on paid ads, but he probably spent hundreds of thousands if not millions on a team to execute this guerilla marketing strategy. This didn't cost $0.

7

Got an email "GCP's Apache Kafka service is now live" at noon. After dinner, spent half an hour confirming it works well with Timeplus. I don't think you can make the bootstrap server publicly accessible. Has to setup a bastion host or run your app within the same project/VPC. Setting up the SASL username/pwd was not easy. Follow the guide carefully https://lnkd.in/gcKEVh3g and you may need to disable the iam.disableServiceAccountKeyCreation Anyway, if your workload are in GCP already, having such Kafka service in GCP is nice way to burn your cloud credits. Yet another Kafka vendor, great.

33

2 Comments

Story time: I talked to Plaid's DevRel team last month I learned 30% of devs who get API access NEVER onboard because they never make it through the integration process. Imagine you're Plaid and you worked super hard to get developers to use your products — but then they quit and use a competitor because yours is too hard. 𝑻𝒉𝒂𝒕 𝒄𝒐𝒖𝒍𝒅 𝒎𝒆𝒂𝒏𝒔 𝒎𝒊𝒍𝒍𝒊𝒐𝒏𝒔 𝒐𝒇 𝒍𝒐𝒔𝒕 𝒓𝒆𝒗𝒆𝒏𝒖𝒆 𝒐𝒏 𝑨𝑷𝑰 𝒖𝒔𝒂𝒈𝒆. This is the problem that we're aiming to solve at Layer. We add an Integration Expert (ie. extension) on top of VSCode to help DevRel teams at companies like Plaid make onboarding devs easier.  Like a cake with icing, VSCode is better with another Layer.

31

2 Comments

Prompting Strategy of the Day coach LLMs like someone who reports to you: Good engineering managers know that if you have given an engineer requirements and have even clarified them and expectations aren't being met the solution often falls out of asking the engineer to walk you through their approach step by step in words not code. Sometimes being able to identify just 10% of what they are missing unlocks the whole rest of the problem. Austin: The test is still failing.   To be clear the issue with  <the input string we are testing and want our method to handle gracefully> is that  <how the small addition I made to the input string is expected to cause a failure in a dependency we can’t control> Before generating more code why don’t you walk me through in words how you are you are breaking up our input string to be able to analyze it. You don't need to tell me how you are analyzing it. I just want to hear the description of how and what you broke out at each step so that, maybe I can help you better. LLM: <explanation> Austin: Ah I see, but are you conscious that, <something incredibly obvious being described that is wrong but that isn't so obvious in the code> If you have completed step 1 then at step 2 you should check first for the presence of  <delimiters that are optional and can appear in most any order>  if neither are present then we are done. But if one or both exist I would check for <the one easy exception to ordering rule that makes finding the solution easier> LLM: <provides code fixes the problem at hand but also that exceeds expectations elsewhere>

3

When I saw this AND there was going to be a video... I am not going to lie. I was expecting FUD. Well done to Filip Hric and Jonathan Canales on keeping it a little sane which is not what I expect when I hear people talking about Cypress.io vs anything. I spend a lot of time looking at ALL frameworks out there to make sure the web is a better place tomorrow than it is today. It's why I enjoyed working at Mozilla and enjoy working at BrowserStack. One of the key things that I liked from both presenters was the fact they expected moving to a new framework from Selenium would make things better but over time it went back to being as flaky as it was with Selenium. Filip even admitted he, as an ambassador, never mentioned that part as it wouldn't look good on blog posts. Even Jonathan mentioned that people moving frameworks if they were to rewrite things using their existing framework with modernised patterns would lead to less flaky tests. Pick the tool that fits your needs, not the shiny one. Being able to break down web apps for testing is a superpower, not what tool you use. I wrote about this before on my newsletter https://lnkd.in/eE2kM5bY? Anyway, Kudos to Jonathan and Filip for not allowing the FUD to creep in!

42

4 Comments

I'm starting up a newsletter for Excalibur.js news! Sign up for a monthly recap of all the cool gamedev stuff! https://lnkd.in/gKTNuRbs #excaliburjs #gamedev #typescript

4

I find interesting the hype about counting downloads for a given tool as a metric for success. I guess it helps to show how popular something is, but I would love it if people also considered other aspects, such as project governance and project activity. Anyway, let's follow the trend (evidence in the comments): - Selenium Java downloads: 98.5M in May 2024 - Selenium active users in the last 30 days: 2.6M. Happy automation!

54

9 Comments

Been seeing PropelAuth pop around a bunch and boy do I love auth. Always like new players in the game. Let's take a quick look. Pricing. I don't get it. The first tier is 150/month for 2.5k mau. 6c an MAU is pretty crazy expensive esp given most competitors offer 10k for free... The feature breakdown between tiers is also a bit confusing. Some features which seem critical to building an app are behind paywalls where as others which are "nice to haves" are in the free bucket. Unlimited orgs is nice I suppose but that cost is just built into the MAU pricing. Maybe I don't need unlimited? I know Clerk charges way more per org but their MAU's are almost free in comparison. Features. Outside the usually suspects, (2FA, SSO, email, RBAC, etc) the API key stuff was pretty cool esp if you are setting up a dev focused product. Waitlist feature is also a nice little touch. I think most waitlists are disgustingly complicated for their purpose and it is cool they have this on the free tier. It would be nice if there was a drop in UI to let end orgs manage their own users but I couldn't find that anywhere. Clerk has this but it was a little janky in my experience. Docs. The setup is awkward or maybe more so strange. When i go to quickstart I see all these warnings about framework selection. It took a solid 5 minutes before I realized there is a selector in the UI. Using what appears to be a HOC withAuthInfo, seems again awkward at least in the react realm unless I am missing a reason for this. I'd strongly recommend dropping all the HOC usage esp given their are hooks which do the same. Backend was pretty simple. My 2c after an all be it brief review, docs need a bit of love. Which features fit into what payment bucket could also use a review. Clerk and everyone elese for example let me have a staging env at the free tier given it is kinda a requirement to move anything to prod. Little odd to gate that behind a 150/month paywall. It is actually kinda a complete non-starter for any project. 2FA is not needed for a free tier and could easily move to a paid feature. The target customer seems to be anyone launching a very early enterprise developer focused product. A waitlist with unlimited orgs and built in api keys hits many of the fast path needs for a GTM play in that space. The per mau cost isn't as important here but the feature bucketing is strange and would be a non-starter for me. I wish propel the best of luck as auth certainly needs more innovation. It is my least favorite part of building an app.

2