James Larcombe

Not many people know the story of "why" Zenhub exists...so here it goes👇 Back in 2014, the team that would come to be "Zenhub" was a scrappy group of devs and PMs working at a product studio up in Vancouver. When clients are paying you to do work, they (rightfully so) want to understand where that work is at and “when is this going to be done?” The problem was that we could never answer that question… No matter what project management solution we tried (and believe me, we tried them all), we kept coming back to the same core problem. Context switching... Ie. our devs always felt like they were being forced away from where they were working from (ie. GitHub) in order to update our PM tools. So they didn't update them. Needless to say, this wasn't leading to a productive relationship with our clients. So our devs got together on a weekend to try and fix the problem. What they hacked together was a simple Chrome extension to bring a Trello-esque "task board" into GitHub. And as they say, the rest was history. Well, not really, but we’ll save that story for another set of posts… Reducing context switching has been core to our mission from day one. But while GitHub was the home for teams back in 2014, that's changed. Today that home is Slack. While I know people have a lot of mixed feelings about Slack, it has (for better or worse) become where “work” happens in most modern organizations. That’s why today, we’re announcing early access for an entirely new Slack integration that’s going to be a game-changer for how teams use Zenhub. While platforms evolve, that idea of “reducing context switching” has remained a constant, and we’re excited to double down on that mission with Slack. With this new integration teams will be able to create, plan, and track work in Zenhub all without having to leave a Slack channel. If you want to get hands on with what we’re building and join our early access program, check out the link in the comments below. #slack #github #developers #agile #scrum #projectmanagement #devex

62

9 Comments

If I was an A player / high performer seeking employment right now, I'd look for jobs at organizations running one of these business operating systems: Scaling Up: A Gazelles Company, Metronomics, or EOS - Entrepreneurial Operating System. There are several reasons for this: -Core Values-Driven CEOs: Many will have CEOs that actually live their company core values (and insist everyone else does, too), giving you the best chance possible to thrive -A Player Team: Because these organizations are more likely to use Topgrading to hire, you'd be part of a drama-free, A Player team (do not underestimate the importance of this; if you've had bad team members or have been dismayed by workplace drama, you understand) -Get Paid More: Compensation will likely be at the high end for your role because these organizations understand the value the A Player creates -5D Focused Leadership Teams: Leadership teams are focused on Overcoming the Five Dysfunctions of a Team, resulting in less workplace politics (doing the wrong thing for the wrong reason) and way less stupidity from leaders All of these things will result in the most fulfilling working environment you've ever had. Remember the "Great resignation"? That may as well have been a myth to my clients. Why? Nobody leaves an A player team. NOBODY. That was a problem for companies that don't live there core values and that tolerate B and C players. Unfortunately, there isn't a public list of these companies. That would be one incredible A Player recruitment website. But there are a few things A players can do to find these employers: 1. Reach out to the organizations above to find out if they know of companies in your area using their systems/tools 2. Reach out to your local chapter of Entrepreneurs' Organization or Young Presidents' Organization - that's where the self-aware leaders using these systems/tools congregate ***Important interview question all candidates for all candidates to ask: Is your CEO a member of EO or YPO? Self-aware leaders tend to join these peer learning associations, and that's the kind of leader you generally want as an employer/leader.*** 3. Reach out to Metronomics, Scaling Up, or EOS coaches in your area to find out which of their clients is currently hiring. I'll be posting some of my clients' open positions - as well as background on the company - here in the near future. Find a company that is deserving of your behavior and talents. #Metronomics #ScalingUp #EOS #Hiring #JobSeekers #Jobsearch #employerofchoice #topgrading #fivedysfunctionsofateam #corevalues #YPO #EO #Grovertalent #talent #Aplayers #Aplayerhiring

36

6 Comments

🚀 Exciting news, LinkedIn family! I am about to hit a milestone of 400,000 YouTube subscribers in under a year, and I'm eager to share how I did it. The secret? YouTube Shorts. 📊 To achieve this, I committed to posting at least two original Shorts every day. Each Short, about 35 seconds long, maintained an impressive average view duration of 80-95%. Consistency paid off, and after about 6 months, the difference was clear. 🛠️ My channel focuses on the latest and coolest PC parts, custom builds, and repairs. When creating Shorts, I ensure they are either entertaining, informative, or engaging. This strategy captivates my audience and teaches them something new or tells a compelling story. 💡 Leveraging analytics and engagement was pivotal in understanding viewer preferences and optimizing content for better engagement. Regular interaction through comments and live Q&As helped foster a strong community. 📈 This journey has not just skyrocketed my subscriber count but has also significantly boosted my business profits, revenue, and overall success. I’ve recently started offering personal social media content creation packages for businesses and individuals aiming to replicate my success. 🚀 Building a successful YouTube channel goes beyond views and subscribers; it’s about creating a community and consistently delivering value. Interested in detailed strategies or looking to collaborate on content creation? Feel free to connect or comment below! 👍 If you find this journey inspiring, please like, share, or comment. Check out my YouTube channel, TikTok, Instagram, and website for more content!

20

2 Comments

Most companies I speak with are already processing at least a few ACH payments in BC or GP, but they are often unaware of the risks they are potentially exposing themselves to... It's a common theme when I get on a call with a potential customer. Initially, I used to let it slide, assuming they were aware of the risks. However, the more conversations I have, the more I realize that many are not aware of the potential holes in their security: 1. Direct Access to Vendor Banking Info: This happens both during the initial entry of the data and while storing this sensitive info directly in GP or BC. 2. NACHA File Handling: At the end of the day, NACHA files are just text files that can be easily modified, opened, or stored on an insecure computer. To boost your security: 1. Encrypt Vendor Data: Keep this data obfuscated from all users if possible. 2. Encrypt NACHA Files: Secure your payment files to prevent unauthorized access and modifications. 3. Utilize Direct ACH via SFTP: This method not only encrypts file transfers but also minimizes human handling, reducing risk. Having been exposed to the ACH process through Fidesic, I assumed this was the norm with other companies as well, but I've found that most clients do not have these measures in place. If you're concerned about your payment process, I'm happy to chat!

10

2 Comments

THESE will make you a high quality candidate for software engineering... Coachability. Soft Skills. In my conversation with John Vandivier, he highlights that these two traits of software engineers really help you stand out. John has found the research on post-secondary and alternative credentials highlights a skill gap in soft skills. That is, between traditionally educated and alternatively educated individuals in the eyes of employers, one of the biggest skill gaps observed is not technical... but soft skills! What are your thoughts on this? 👇Check the comments for the full video!👇 ---- 🎬 Check out Dev Leader on YouTube for multiple full-length videos weekly! 🗣️ Share with your network! #SoftwareEngineer #SoftwareEngineers #SoftwareEngineering

15

7 Comments

When I first heard the term "Quality Engineer" getting popular a couple years ago, I was a bit skeptical. I know my Canadian friends do not like the term "engineer" for those of us in software development. And I'm hesitant to label anyone so that they sound like they're "in charge" of quality. I was persuaded to embrace the term by João Proença in his talk at ATD USA about it. And this post from Katja Obring also makes a great case for it. https://lnkd.in/eZP4XVKF I do think this is a big part of our future as testing specialists. (and hello, Alan Page and Brent Jensen, I like your "testing coach" term, and personally, I also like "testing consultant"). When I introduce myself, I still say I'm a tester by trade. And, I do think we need a term that conveys the huge contributions QEs/testing coaches/testing consultants/quality advocates make to their organizations. #HolisticTesting #AgileTesting

122

47 Comments

This is a final reminder for the October 2024 Montreal.rb Ruby Meetup, "Tame Complex Queries with Database Views", taking place tonight at 7pm at Anticafe, Montreal: https://lnkd.in/dXhQ6k2G Please remember to follow these instructions when you arrive at Anticafe by 7pm (294 Saint-Catherine St W, 3rd floor, Montreal, Quebec):  - Upon entry, please check in on Anticafe's computer in the 2nd floor (free coffee and snacks are available in the 2nd floor).  - After checking in, please head to the 3rd floor to attend the Montreal.rb event  - When the talk ends (around 8pm), please leave immediately to the Networking Event location next door: NYKS Bar (1250 Rue de Bleury, Montréal, QC) - Upon leaving, please mention that you are with Andy to have your fee covered by Montreal.rb. The event is maxed out already, so if you haven't RSVP'd, you can RSVP for the next month's event instead, before the topic is chosen (if you are a Software Developer with 6 years of experience, you are welcome to present; just submit a title, description, and bio to get your talk booked): https://lnkd.in/d7RrRnQW See you all tonight! #ruby #montreal #meetup #talk #rails #db #sql #database #databaseviews

1

4 Comments

Returning from your annual leave to the news of a mass layoff is not easy, even if you have not been impacted directly. While I am sure this decision was not taken lightly and I could not agree more with what our CEO Dax said below about all the people we hired at Lightspeed over the past few years, it will take a while for those of us who are still here to go back to business as usual. Until then I need your support! This is where you all potentially come into play as my LinkedIn network: To my HR & Recruitment connections across EMEA & NOAM (Germany, Netherlands, UK, Belgium, France, USA & Canada) please email our talent directory [email protected] or reach out to me for more information if your company is hiring for various positions across most departments. As a recruiter, it is hard to see folks you hired and worked with being let go, and as a colleague even harder.... To my former colleagues who were impacted, if you need any support with your CV, need an intro email to someone I might be connected with who has an open position at their company or just want to chat, please reach out. ... also please remember you are so much more than your job!

44

2 Comments

Code coverage doesn’t tell you as much as you think. Mutation testing sounds like a good verification measure. Has anyone used a mutuation testing framework for C/C++ or do you use Test Driven Development? Seems like TDD is the best approach.

5

Predictability is the most insidiously destructive force in software development. I recently wasted $3k on 2 failed attempts to waterproof my basement. Finally the 3rd attempt was successful. Total cost of $9k, 2 weeks of duration, 2 walls to refinish. This, just a week after being laid off. I was super frustrated by the multiple attempts and "hidden" costs. But after finding my chill, I had an epiphany. Demanding certainty would have made it much worse. Additional work to create an "accurate estimate": - Run cameras up all drain pipes to fully inspect their flow - Dig up the pipes to manually inspect where the camera couldn't reach - Manually saturate (with a hose) each wall to try to reproduce the leak - Tear out every finished wall to inspect the concrete wall surface - Dig down to the foundation to inspect the footer drains directly Call it 3-5 days of work, at least $10k. I'd also have to re-grade / re-seed my yard and refinish the walls. And the basement would still be leaking! The point: predictability is EXPENSIVE. The contractor knew this and instead of wasting my money on estimation accuracy, they ran a $3k value experiment. Saved me 1000s. And yet… in sw development (arguably MUCH more complex), we insist on optimizing for predictability, front-loading knowledge work so we can accurately forecast how much hands-on-keyboard work can fit in an arbitrary 2 week window. Spending as much (or more) on work breakdown so we can accurately measure throughput. Cutting corners to meet the deadline. Squeezing out slack time required for sustainable pace. Reducing sw dev down to order taking, killing the spirit of innovation. Burying agility under layers of process and governance. And in the end, did we even fix the leak? 🤷‍♂️ In Software Engineering, we've fully automated the predictable parts already. What's left is R&D.

66

22 Comments

New Tutorial: Setting Up Templ Using Nix Flakes. I'm on a little side-quest to see if Go (and/or Rust) are a viable alternative to a NodeJS or PHP heavy stack for small-scope/heavy-traffic websites. While setting up Templ I figured this was a good topic for a Tutorial. P.S. Also peep the new cherry blossom theme! https://lnkd.in/gG8R2QuA

2

The only time CTOs & engineering managers want to be really good at SALES When they need to sell TECHNICAL DEBT to CEOs and business teams. High Technical debt is #1 reason why engineering teams fall apart - Forces developers to spend all their time fixing past issues - Makes developers too scared to touch code or make changes - Brings down release speed slowing progress, and - Destroys dev morale in the long run Every engineering leader KNOWS this but business teams are simply not interested to let them budget time on what they think has zero value. Why. There are million things to fix and there is never enough time and resources, so why bother about something like technical debt. Even when technical cofounders argue that 'we need to take care of it because it is there', it gets no attention. Maybe it is a SALES problem. Every CEO will deeply care about: - losing customers or revenue leak - losing quality engineering talent - losing business momentum or not able to get on that J-curve Maybe technical leaders need to explain to CEOs how all these & more are side-effects of technical debt. Maybe that helps it get attention. #hypertest #technicaldebt #softwareengineering #startups #successmindset

26

The cost of poor quality is far higher than the cost of good #QA. At Quarry, we've seen firsthand how good QA can make or break a project. Why is QA so crucial? Let's break it down: Bugs are expensive. Catching them early? That's just smart business. User experience is everything. QA ensures your site works as smoothly as it looks. It's your reputation on the line. A glitchy site with delays is a fast track to lost customers. Security matters. QA helps catch vulnerabilities before the bad guys do. It saves time and cost in the long run. Trust us, fixing major issues post-launch is a hassle. QA isn't just about finding bugs. It's about ensuring your product meets your objectives and delights your users. But here's where it gets tricky: Many organizations undervalue QA. They see it as an extra cost rather than a necessary part of the process. We do things differently. At Quarry, QA is baked into our process. It's not an afterthought — it's a core part of how we deliver value. Have you ever launched a project without thorough testing? #QualityAssurance #WebDevelopment #BestPractices

1

Yesterday, I put my hardhat on and got to work. No, not metaphorically speaking... I mean that in the actual sense (see photos for proof). We had a strategic on-site for our team here in the Vancouver area. [We're all remote in this part of the world, so we don't go offsite, we go onsite]. The theme: It is time to work. We rented out an industrial warehouse space and old-schooled it without Google Slides. The one rule: if you were standing, you had to put your hard hat on. After all, if we're building the "factory of the future" in which so much of the business will be automated, the "factory of the present" is a dangerous place to be. As such, ensure that your head is always protected. I say often, including on our website over here at www.TravelAI.com, that the factory of the future will consist of one man and one dog. The man's job is to feed to the dog. The dog's job is to ensure that the man does not touch the machine. In the age of AI, humanity's job will be to infuse the soul into the machine. Thus, very much related, I thoroughly enjoyed @shaanpuri's post from earlier today about showmanship: It is easy to take yourself too seriously in work and in life. Sometimes all that it takes to stand out is to put on a hard hat, and do the damn work.

37

5 Comments

I tried TDD for years—and this is what no one tells you: 1) Full coverage isn’t a shield—it just looks nice on paper. 2) Bugs love slipping past the most confident tests. 3) Maintenance is harder when your tests don’t tell the story. 4) TDD only works if you stick to it—and most don’t. 5) The best developers aren’t the ones with 100% coverage—they know where it matters. 6) Code evolves faster than tests can keep up. 7) Unit tests don’t find all bugs—just the ones you thought of. 8) Writing tests can save others more time than it saves you. 9) Unit tests document your assumptions more than your logic. 10) Sometimes deleting old tests is the smartest move you’ll make.

1,443

173 Comments

The Q3 slump hit hard—BTC drifted sideways, dipping to $48.9K before bouncing back to test $64.5K in September. But even with that bounce, the sell bias stuck around—88% of trades were client sell orders, as to BC. Market's clinging to BTC, ETH, and stablecoins, which made up 87% of trading flows. Still, there’s some heat in the altcoin space. Coins like SUI and SEI popped off with 3X gains, showing there’s still action if you know where to look. On the options side, traders have been biding their time to take directional and vol trading opportunities when volatility kicks in. Q4 could deliver such an opportunity, and if that happens, we expect more covered call sales and upside bets as traders lean into the possibility of a rally driven by the elections. October and November have a track record of delivering major BTC gains—averaging 22.9% and 46.8%, respectively. Pair that with a Fed cutting rates for the first time in four years and another cut possibly on the way? I’m closely monitoring a strategic mix—derivatives to capture opportunities when volatility spikes, and spot markets in more stable assets like BTC and ETH if consolidation persists. Also keeping a sharp focus on mid-range altcoins, particularly those with TGEs delayed into Q4 2024 and Q1 2025, as they could benefit once macro conditions stabilize. Should the Federal Reserve maintain its current stance of higher rates and constrained liquidity, volatility could increase significantly. In such a scenario, we could experience a potential upside closer to the end of 2024, possibly paving the way for high-reward opportunities in riskier assets when liquidity eventually returns.

16

I had a great conversation with Evan M. about my career and entrepreneurial journey, including getting into the venture capital industry and why I founded Staircase Ventures with a unique philosophy and approach. Some quotes: "We benefit in Canada from terrific technical talent. In addition, we are seeing more repeat entrepreneurs and more experienced start-up leaders than we did 5 to 10 years ago... The other thing is that US investors want to invest in Canada. Ten years ago, US investors were reluctant to invest in Canadian companies and if they did, it would be on the condition that they move to the Valley. That is no longer the case." "I started my own fund not for the sake of starting my own fund, but because I wanted to devote my time to working with entrepreneurs and to serving them, helping them to build impactful companies. I had some ideas about how venture could be done differently and I wanted to put those ideas into action. That is what led me to start Staircase Ventures... There's three unique aspects of Staircase Ventures. The first is our founder development platform which is designed to help accelerate founders' development and help them perform their best every day." "Life is long and how you treat people and how you perform really, really matters in the long run. Life is not a short-term game; it is what you do and how you show up, day-after-day, over a period of many years that will determine your future." Listen here: https://lnkd.in/gpHprCt8

68

4 Comments

The October Montreal.rb talk will be on how to "Tame Complex Queries with Database Views", given by David Cornu, a Staff Software Developer at Patch. Date/Time: Wednesday, October 2, 2024 at 7pm Location: Anticafe Montreal (294 Saint-Catherine St W, Montreal, Quebec, Canada) RSVP link: https://lnkd.in/er8Hz24N Description: PostgreSQL views are a useful tool to make query logic reusable and maintainable. This talk will cover their pros and cons, a couple of real-world use cases, and how to use them in Rails apps using the Scenic gem. Speaker: David is a staff software developer at Patch (a climate tech startup). He cracked open Why’s Poignant Guide to Ruby in 2009 and has been in and out of Rails apps since. #montrealrb #montreal #ruby #rails #talk #presentation #softwareengineering #softwaredevelopment #programming #community

1

👋 Writing an honest and transparent LinkedIn post about recruiting is 𝚒̶𝚖̶𝚙̶𝚘̶𝚜̶𝚜̶𝚒̶𝚋̶𝚕̶𝚎̶ always tricky—so I’m going to try my best to share our vision for this new 𝗙𝘂𝗹𝗹-𝗦𝘁𝗮𝗰𝗸 𝗝𝗦 open position at Roundtable. We’re looking for a Full-Stack JS Developer to join our team. But this isn’t just about writing code or shipping features—it’s about bringing something extra and helping us grow as a team. 🚀 At Roundtable, we’re building the marketplace and legal infrastructure for private market investments. For this role, we’re not just looking for another great developer. We’re looking for someone whose expertise and perspective can amplify what we’re already doing, challenge us where we can improve, and complement our strengths as we scale. 🎯 What we’re looking for: We’re looking for someone who: • Brings deep expertise: Whether it’s working with large JS monorepos, mastering the latest features of Next.js, shipping production-ready apps with Expo, or tackling FinTech challenges like equity management or transaction logs, your experience will be invaluable. These are just a few examples—there are so many areas where expertise could make a big difference. If you’re curious, feel free to DM me to discuss how your skills could fit! • Inspires growth: You’ll have the chance to share your knowledge and mentor others, while also finding opportunities within the team to push your own skills further. • Complementarity, complementarity and complementarity: This isn’t about coming in and rewriting everything. It’s about finding the right balance of shared goals, unique skills, and fresh energy to move us forward as a team. 💡 Why join Roundtable? • Impact that matters: You’ll shape not just the product, but also the way we work together. • Opportunities to grow: If you’re curious, ambitious, and eager to take on new challenges, you’ll find plenty of space to learn and thrive. • A culture of collaboration: We believe that sharing knowledge, learning from each other, and working together makes us stronger. 🧩 Who’s a perfect fit? If you’ve already shipped robust production apps, tackled complex FinTech problems, or have advanced knowledge of tools like Next.js, Expo, or JS monorepos, this might be your next challenge. But these are just examples—we have plenty of areas where specific expertise could bring huge value. Know someone who might be a great fit? Tag them in the comments or DM me for more details! 📩 👉 My cofounders Evan Testa and Julien Fissette have very recently shared other cool open positions here at Roundtable, and my incredible team members have also posted about exciting roles we’re hiring for.

54

3 Comments