anoop K.

The best use case for overseas development I've heard: We have customers in the eastern hemisphere. To support those customers better, we're standing up product, dev, and support teams to help serve those customers needs. Two key ingredients in making that successful: commensurate pay and the same level of performance and accountability as US peers. #software #international #teammanagement #overseasdevelopment #startup #leadership #coaching

6

This product was practically built for me. I’ve been waiting for something like it for years, long after I gave up writing on paper almost entirely. Heck, if it wasn’t for having kids, I probably could have gone the last the past decade with the challenge of not writing anything down on paper. Which makes it all the more frustrating at the price point it’s released. This isn’t targeted for grade school students, college students, or young professionals. It’s targeted at prosumers which share the same space as an iPad Air, and the market is already dominated by prosumers who want that product. For those who can’t afford the iPad, Amazon releases tablet computers in the $100 range. I know Remarkable is a much smaller company, and can’t compete on price with Amazon, or volume like Apple. But waiting so long for something I can’t justify the purchase price just hurts. At half the price it would have been a no brainer. It checks practically every box.

11

5 Comments

Recently we had a production issue on a website where there was a high amount of traffic generating a 404 response (the orange area in the graph below). I noticed that there were repeated requests for the same page, and they never came from the cache. This lead me to the question...why is the 404 response not cached? I did some investigation into this and learned about a security concern when the 404 page is cached (essentially it is possible to create a denial of service by sending request for resources that a user doesn't have access to). I did a little post on my blog which elaborates on this a bit. Hope you find it useful https://lnkd.in/gSnTdFsH

67

15 Comments

Wondering about #PlatformEngineering hidden traps? I share some thoughts on the matter with health tech magazine. To me this reculumination of central SOA team with a twist. Your customer are internal developers and business users. DM if you would like to discuss more.

13

Looking to get started with in-database machine learning with MySQL HeatWave? This guide will help get you on the right path. https://lnkd.in/gPjuJU9g

1

All the small web shops should look into this as a funnel for new biz and all the small and medium size businesses should really consider where your best ROI is at. Fix it and be accessible!

8

In late 2023 we reported that MySQL and MariaDB’s REPEATABLE READ did not, in fact, provide repeatable reads. The MariaDB team has been hard at work this past year. They’ve added a new flag, --innodb-snapshot-isolation=true, which causes REPEATABLE READ to prevent Lost Update, Non-repeatable Read, and violations of Monotonic Atomic View. Jepsen has not yet tested this, but it looks like MariaDB might, with the new flag enabled, offer Snapshot Isolation at REPEATABLE READ. https://lnkd.in/dw_SFhjh https://lnkd.in/dc_9-P26

57

on hiring an ea While companies like Athena and Wing are popular options, they come with challenges I didn't like: * Time zone differences * Cultural gaps * High initial costs ($3000+/month) Instead, leverage your network. Tell everyone you know that you're looking for an EA. You'll be surprised how many qualified candidates are already in your circle. Plus, working with someone who understands your culture and timezone is invaluable. Two crucial tips for success: Document everything. Create clear SOPs using tools like Notion or Loom. This makes onboarding smoother and sets clear expectations. Start small and scale up. Begin with a capped number of hours at a set rate. This lets you build trust and understand your needs. (Trust me - once you find someone great like my EA Maria, you'll wish you had more time with them!) Bottom line: Start with who you know, really just ask everyone for referrals first, document well, and scale gradually

6

The First Decade of Serverless Innovation Let’s roll back the calendar and take a look at a few of the more significant Lambda launches of the past decade:

2

This resonates so much. No, you can't do it all, especially not at a startup. Since COVID I see so many people try to balance unaided parenting with full-time careers, and no, I don't see anyone doing it well. My kids are now 17, 13 and 10 and just now, when they trek to most of their activities on their own, and do their HW on their own, and cook their own meal or snack, we have finally let go of the outside help ( and this is with both parents working from home for last 5 years, outside of peak COVID lockdown, we had always relied on a designated childminder outside of school hours). Yes, working remotely does mean that I have more time and flexibility in my life, it means I can walk my kids to school sometimes, or have breakfast with them instead of rushing to the office, it means I can go and see their midweek concert at school, or be there to grab them from school on a sick day in 10 mins. But it also means that on EVERY day basis we all need clear boundaries, work hours, dedicated spaces that are not continuously invaded by children, or feelings of guilt that our children are unattended. One thing that a lot of the arrangments lack is transparency, being explicit with ourselves, our partners, our managers and colleagues on when we are making trade-offs. What helps is verbalising our plans, putting explicit blocks on calendars for pickups, doctor's appointments and school activities, letting others know when you will have periods of diminished focus due to a school holiday or a sick kid at home, and ruthlessly prioritising. Very few of us can claim to be at Julius Ceasar level of multi-tasking. Flexibility of remote work ≠ combining full time work with full time parenting

26

🌟 From Raw Data to Behavioral Predictions—Effortlessly What if AI deployment didn’t require months of preparation? With BaseModel.ai now on the Snowflake Marketplace, you can transform behavioral data into predictions in just a few clicks. ✅ Rapid Deployment: Build and deploy models in a week.  ✅ Scalable Flexibility: Create multiple models for diverse use cases.  ✅ Privacy Guaranteed: Data never leaves the secure Snowflake environment. Say goodbye to complexity and hello to actionable insights. AI for behavioral data has never been this simple. 👉 Try BaseModel.ai Today  #AI #MachineLearning #BehavioralData #BaseModel #Snowflake #Synerise 

39

4 Comments

Some SaaS software subscriptions are like signing up for an email list in order to get a discount: easy to sign up for but difficult to cancel. Has anyone come across any hidden or misleading terms & conditions for software?

3

Last Tuesday, Malsgufa, our legacy CMS backend, was shut down. This milestone for BI's Tech and Product team culminated years of planning, effort, and execution. Malsgufa's first commit was on July 25, 2014, leading to 5,186 commits across nearly 30 repositories. Built and maintained by scores of engineers, its deprecation represents significant cost savings (20 production replicas, 3 instances of Solr, and an insane number of Zookeeper instances!), reduced security risk, and the elimination of an often-blamed boogeyman. The journey began in January 2020. Our challenge: moving traffic off Malsgufa without rebuilding everything in Muse. Initially, we tried GraphQL as an intermediary between Viking and our services, but progress was limited by Viking's complex Angular/Vue architecture. In January 2023, we pivoted to the strangler fig pattern with a shim. This approach proved far more effective – all Malsgufa traffic went through the shim first, with verbose logging to track unhandled requests. Meanwhile, we built Story Versioning API (SVAPI), incorporating lessons learned from Malsgufa's limitations around history and publishing states. We ran four major migrations (stories, custom pages, slideshows, and videos), building support in Muse and shimmed compatibility for Viking. Traffic gradually decreased from a torrent to a trickle, leading to the gloriously uneventful shutdown. Next, we will deprecate Viking by Q2 2025, unifying our users in the Muse ecosystem to create the industry's most innovative CMS. Special thanks to the entire Story Creation team: Chase Gruber, Chris Speziale, Daniel Arita, Danny Feliz, Dasha Lary, Dawin Camillo, Eric Saam, Frederica Chen, John Laslo, Kelly Filush, Morgan Cohn, Sarah Pai, Tyler Greenfield! Thanks also to DaD, Engagement, Helpfulness, Cloud Engineering, Test Engineering, and Operational Excellence! Finally, we recognize Malsgufa itself. Developed as a unified CMS backend to support Business Insider's expansion into new markets, it served our global newsroom reliably for a decade, publishing millions of stories despite no major changes in recent years. While it became less sustainable as our business evolved, it deserves our respect. Thank you, Malsgufa. May you rust in peace.

41

6 Comments

Oso makes this look easy. Historically you either put all of your data into your auth system which is easy, but creates availability and privacy issues, or else you distribute your data which was scalable and secure, but leads to spaghetti authorization logic and complexity for developers. Such a nice balance here. The CAP theorem of authorization?!

4

I’ve been doing a lot more recruiting and one trend I’ve noticed is a tendency to talk about using a framework when really describing a process. There are two key differences: Frameworks are structured but open ended and are not prescriptive. Processes are prescriptive sequential steps. It’s important to identify when you want to use one or the other: - Coaching an engineer: Framework - Planning: Probably framework with a tiny bit of process for scheduling - Recovery of a data center: Process A more engineering centric / systems view would be to look at frameworks as the interfaces in engineering and process as the implementation behind the interface. Too often we’re focused on the implementation of the process before we’ve established what the framework is we want to use.

49

3 Comments