Bapi V.

I think that maybe a better choice than cynicism about the state of tech, for me, is to finally embrace entrepreneurialism. I literally have all the required skills to be an entrepreneur from a technical basis. I can write the code, build the site, deploy the servers, implement and monitor the observability stack, and quash the bugs. I am, in all lack of humility, one of the most talented software developers I've ever met (even when employers don't agree; the number of times my *fellow coders* tell me I write the most elegant code they've ever seen is all the proof I need, from a cohort I actually respect). All I'm really lacking is some business knowledge, and... knowledge can be acquired. Sorry, MBA's, I don't see what you do as all that complicated; I've mastered much more complicated concepts before. I just don't LIKE it, but there are plenty of things I do (and am good at!) despite not liking them. I think I've just been intimidated at the prospect of learning something (managing employees, let's say, or corporate tax strategies) that is so 100% out of my normal wheel house (software development). But lack of confidence will kill you almost as quickly as overconfidence, and I'm a survivor! The thing is, I don't have to -- and I'm not seeking to -- "get rich." All I want is a job that I believe in, where I respect the employer (me, in this case!), which earns me enough money to live my life the way I want. And I'm not looking for "champagne wishes and caviar dreams." Caviar is gross, and I don't drink any more. I'll settle for "pays the mortgage and buys me food, and lets me take a road trip every once in a while as I manage the company remotely." And I will NEVER be publicly traded. Wall Street ruins everything it touches.

Today was a hard day at the Reality Labs-Research office in Toronto. Unfortunately, I was one of the many impacted by the recent Meta layoffs due to company realignment. I didn’t get a chance to say goodbye to anyone formally, but to those of my (now former) colleagues reading this: I will thoroughly remember this amazing experience and hold on to it dearly, what a privilege it was to work with you all. I can't thank you enough. This last year I've been working in the best AI research team in the world, it's been a crash course on so many new realities for me. I got to pick the brains of, and collaborate with some of the most brilliant AI researchers in the world (you’d think this was an exaggeration, but it’s not). Program Managers at Meta are unsung heroes and I have learned so much just by watching them put out fires with ease and collaborating with them every day. I made so many good friends along the way as well. The kindest, most humble, patient, intelligent, and results-driven people I’ve ever met. I will truly reflect on this experience fondly. I leave Meta knowing I made an impact on research that is already shaping the future of how we interact with the world. It was amazing being a part of something so big, I will miss working with you guys dearly. Jessica Kishimoto Séréna Bochereau Julian Geoffrey López Cherise Forshay Cameron Lynch Jackson Rushing Kathleen Buckley Ken Suong Cheryl Lao Alexander Bakogeorge Kevin Carlberg Eric Gan Stefan Scherer David Marques David F. Caley Drooff Matt Hanson Yuxuan Sun Nick Raines Karl Ridgeway Tyler Simpson Allen Bolourchi, PhD, MBA Joseph Tighe Joey Greer Riley Williams Xuanyi Zhao Alejandro Castillejo Muñoz Vivian Lee Michelle Li Christopher Collins That being said… I am looking for something new. I’m passionate about driving software teams in highly cross-functional environments and I'm an experienced Technical Project Manager with 3+ years of experience in #tech, #AiResearch, and #software. For those of you in my network, those I’ve worked with in the past, those I’ve collaborated with, I ask that you share or interact with this post to help me gain visibility as I navigate my next career step. I’m looking for roles in: #ProjectManagement #TechnicalProjectManagement #TechnicalProgramManagement in #Tech.

220

21 Comments

I had an interesting discussion with folks from the Chrome and Firefox teams about React Server Components and how they affect the web performance at the Toronto Web Perf Meetup yesterday. The DCL event seems to happen when the last bit of HTML reaches the browser, which can be seconds later. Until that happens, no module or deferred scripts are going to be invoked. Having the browser paint the page before all suspended components load is definitely a good feature, but it doesn't change the fact that we need to deliver all data as fast as possible. All the deferred or module scripts won't load until DCL happens. Have this in mind when you're suspending your components. It's easy to think "it will reach the browser whenever it does" since the users will be able to interact with the website before that, but don't adopt that mindset.

25

Curious about how much you could earn annually? It’s time to unlock the potential of your hourly wage! As a co-founder of Tivazo, I’m excited to share our Hourly to Salary Calculator, a simple tool that helps you see exactly how your hourly pay translates into a yearly salary. Whether you’re budgeting, considering a job offer, or planning for the future, this tool empowers you to make informed financial decisions. 💰 👉 Ready to find out? Click the link below to discover how the Hourly to Salary Calculator can work wonders for your financial clarity. #FinancialPlanning #SalaryCalculator #HourlyToSalary #EarningsInsights #Tivazo #tivazomedium

8

1 Comment

While half of Canadians scrumble whether it is a good idea to become a 51st state, the other half is confused by USD at 1.44 I would note that it is not only Canada. For example, loonie is head to head with Euro. It is just that USA is the true accidental superpower. There is a great book on this which I highly recommend (first comment)

5

1 Comment

🚀 Day 4 of 365 Waheguru ❤️ Turning a layoff into a $10M business! Today, I worked on registering a corporation. I saw some videos and resources on how to register a corporation in Canada. It took some time, but I finally got it done! Streak: 4🔥💪 0🔥🥦 4🔥📚 What’s one unexpected challenge you’ve faced recently, and how did you handle it? Drop your stories in the comments! Stay tuned for my journey from zero to $10M! 📈✨  [365DayChallenge, LayOff, Software Engineer, IT, EntrepreneurLife, Business Journey, Challenge Accepted, Real Estate Investment, Viral Challenge, New Beginnings, Real Estate, Multi million dollar business, REI, RE]

6

A few days ago, I came to a realization: I am not just building side projects; I am creating a portfolio of software products aligned with my interests and skills. Over the past year, I have developed: ✨ MapleStack: A job board for tech jobs in Canada ✨ SpellCheckMySite: A tool to check spelling mistakes on websites ✨ FindChildCare.ca: A directory of child care providers in Canada And now, I'm working on something new - this one a bit more involved than the others (announcement coming soon!). It has made me realize that each project isn't just a standalone creation, but a step in my journey as a builder and problem-solver. It's exciting to see how each project informs and inspires the next. This isn't just a collection of work - it's an evolving body of ideas and solutions.

11

2 Comments

This is something I see time and time again that I think every founder should account for when hiring their core engineers. Every team wants the .1% engineer. Ex-Stanford/Waterloo, worked at top L1s or L2s, polished and in-demand. But then there’s another archetype. Crypto native, non-target school/self-taught, chronically online and grinding at hackathons. Accepted the fact nobody will hire them because their experience isn't there yet so they are heads down on building their own project after working day an night to secure a grant. The first is polished but already chased by everyone. The second? Hungry, relentless, with something to prove. In Web3, where innovation thrives at the edges, I’d bet on the chip-on-the-shoulder engineer every time. The positives/negatives: The .1% engineer: Brings loads of experience, proven success, and a network, but may lack the same level of scrappiness or loyalty when the eventual bigger opportunity comes knocking. The chip-on-the-shoulder engineer: Brings hunger, creativity, and a founder’s mindset, but will need mentorship or time to refine. Ultimately when building your founding team this is a decision you have to live and die by, but you need to understand the consequences of both. Which would you choose anon?

14

4 Comments

🌟 Mastering Mentorship: Empowering Engineers and Junior Talent 🌟 With Shopify recently announcing plans to hire 1,000 interns, many engineers are about to embark on their first mentorship experience. Mentoring junior developers is a rare and special opportunity these days, and it's a chance to make a lasting impact on someone's career. In my latest blog post, I explore: • 𝗪𝗵𝘆 𝗺𝗲𝗻𝘁𝗼𝗿𝘀𝗵𝗶𝗽 𝗶𝘀 𝗲𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 for engineers—it's not just about coding but about sharing knowledge and helping others grow. • 𝗛𝗼𝘄 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝗮 𝘀𝘁𝗿𝗼𝗻𝗴 𝗺𝗲𝗻𝘁𝗼𝗿-𝗺𝗲𝗻𝘁𝗲𝗲 𝗿𝗲𝗹𝗮𝘁𝗶𝗼𝗻𝘀𝗵𝗶𝗽, starting with setting clear goals for both parties. • 𝗧𝗵𝗲 𝘃𝗮𝗹𝘂𝗲 𝗼𝗳 𝗽𝗮𝗶𝗿 𝗽𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴, which allows engineers to practice mentoring and learning in real-time. • And most importantly, 𝗵𝗼𝘄 𝘁𝗼 𝗽𝗿𝗼𝘃𝗶𝗱𝗲 𝗰𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 that fosters growth and builds trust. Whether you’re new to mentoring or looking to sharpen your skills, I hope these insights help you approach mentorship with confidence and purpose. Check out the full post and let me know what you think! #mentorship #engineers #shopify #internships #growth #engineeringleadership #feedback

4

1 Comment

Game planning better offerings through Brock Software. A: 👨‍💻 Development On Demand - pay $7k/month for ~20 sprint points of effort. B: 📅 Rapid App Builds - Mobile, web, or both in 2 months. $29k for one platform, $49k for both. C: 🏗️ (still brainstorming) App Builds On Demand - pay monthly to get an app built (cheaper to get going, maybe around 2-4k per month over a year or so). Any of these sound desirable? Obvious flaws?

24

14 Comments

C++ Next Gen - I recently came across Herb Sutter's latest update on Cpp2 and cppfront. Check it out here: https://lnkd.in/gTabj6sx. I'm excited to see that the C++ next-gen - Cpp2 - is getting evolved. The Cpp2 is a new syntax of C++, which is compiled by cppfront. The compiler builds Cpp2 into standard C++ code. Impressively, C++ and Cpp2 are interoperability i.e. they can be used together like Kotlin and Java, Swift and Object-C. The cppfront promises to be safer and simpler. It introduces interesting features that C++ lacks, such as contracts, metafunctions, and reflection. Here's a snippet in Cpp2: main: () = {    words: std::vector = ( "Alice", "Bob" );    hello( words[0] );    hello( words[1] ); } hello: (msg: std::string_view) =    std::cout << "Hello, (msg)$!\n"; Although it differs from C++ syntax, mastering a new syntax shouldn't take much effort. Looking forward to writing in this new iteration of C++ soon! #cpp #cpp2 #cppfront

7

Public service announcement for non-Canadians: In Canadian English, "sorry" is used a lot. Maybe 30-60% of the time it could be an apology, but often enough, it's not. So let me explain some of those other use cases: - We're trying to be polite - We're expressing sympathy - Something happened we regret - Trying to get someone's attention, usually before making a request (e.g., "Sorry, can you help me?") - Trying to take the edge off a statement (e.g., "Sorry, but I don't think that's a good idea") - Various idiomatic expressions (e.g., "Sorry to say", "Sorry state of affairs", and the classic "Sorry, not sorry") - Sarcasm/Ironic statments -- this is mostly habit or reflex, (e.g., "Sorry, just another traffic jam.") - Habitual/reflexive use cases, like saying sorry when bumping into a person; this isn't an apology, it's just a reflex for many. So in different parts of Canada, these will be used similarly but slightly differently, or more of some than another area. But generally, this is a reference of SOME of the ways we use it. Hope this helps.

3

4 Comments

CircleCI is busy fixing a big outage today. What plans does your engineering org have in place for CI/CD outages? One company I worked for used their own runners, some bare metal in the various offices. It was a hassle at times, but in light of today's outage, it's a resilient solution. What redundancies does your tech company have in place?

4

3 Comments

Pair Programming: The Underrated Power Tool in Development Pair programming might not seem like a conventional "tool," but it's one of the most powerful and underrated strategies in software development. Whenever I pair program with another developer while building on Bubble.io, the benefits are undeniable: Accelerated Problem-Solving: Two minds working together often find solutions faster than one. Collective Intelligence: Pair programming creates a “mastermind”—a shared intelligence that transcends our individual thinking. Automatic Knowledge Sharing: Techniques, shortcuts, and approaches are exchanged naturally, elevating both developers’ skills without formal training. Stronger Outcomes: The collaboration produces cleaner, more efficient builds. As a User Experience advocate and Bubble.io developer, I’ve experienced how this approach can supercharge development—especially with Bubble, a full-stack no-code platform that enables faster, more dynamic product creation. -------------- Have a startup idea? Let’s bring it to life—5x faster with Bubble.io. DM me, and let’s build something amazing together.

4

🧵 The Hidden Developer Growth Secret I Learned From Early Shopify Days (It's not about the tech stack...until it is.) In 2006, I was a young dev in Ottawa running IT services. One coffee chat with Aydin Mirzaee changed my entire perspective on building software. Here's what actually matters: Code Isn't Your Ceiling From: "I need to master the latest framework!" To: "Wait, these founders are teaching me how to think about problems" Learning how successful devs approached problems > memorizing syntax The Real 10x Move From: "Must learn every new tech!" To: "Must understand why this feature matters" Watching early Shopify's obsession with merchant problems taught me more than any architecture doc. Community Compounds From: "I'll just learn online" To: "These local devs are sharing real-world battle stories" Truth: Building alongside others beats watching tutorials. Growth Is Messy From: "Need perfect code!" To: "Need to solve real problems" Plot twist: Those local meetups taught me how to balance technical debt with business needs. Mindset > Stack From: "Ruby vs PHP vs Node?" To: "How are we measuring user impact?" The tech stack debate doesn't matter as much as understanding your users. The Hidden Truth: While everyone's chasing certifications... Real engineering wisdom comes from: Seeing decisions play out Watching products evolve Understanding user impact Building alongside others Sharing real failures What I really learned: Technical skills are table stakes Problem understanding is rare Community beats credentials Impact over implementation Measure what matters Want real growth? Join local dev communities Ask about failure stories Learn decision contexts Share your struggles Build relationships Because while everyone's copying FAANG architectures... Understanding why decisions were made matters more than the decisions themselves. What unexpected lesson changed how you build? Share this with a dev who needs to think bigger 👇 #DeveloperLife #WebDev #Engineering #StartupLife P.S. Great code starts with great problem understanding and the actual need. Everything else is just implementation details.

4

3 Comments