Victor Ivri

Rails 7.2 now makes sure jobs get enqueued after the current database transaction is committed. Previously, your jobs would run before the records were saved to the database causing errors, so Rails takes care of it for you. If you've ever had to remind yourself (or your team) to use `after_create_commit` callbacks instead of `after_create`, this solves that problem. ActiveRecord uses transactions behind the scenes, so it's an easy mistake to make. And with jobs being retried, it's confusing why the job fails then succeeds a second later. This is another great example of conceptual compression in Rails! https://lnkd.in/gyNtiPnr #ruby #rubyonrails #rails

141

9 Comments

Recently, someone asked me for advice about hiring their first engineer. It depends on the industry, of course. My advice is - don’t hire a Shopify developer. Hire an engineer. A good engineer can learn APIs, a new language, or whatever they need to, rather than the other way around. Look for a breadth of projects, but dive deep into one or two projects they’ve done. You need to know how passionate they are about their job. My favorite question to ask is, “Tell me about a project that you’re most proud of.” What is your favorite question to ask when hiring someone?

30

9 Comments

Is your MS partner using Copilot for development? Here’s why this should be a criteria when selecting a partner: “On a feature for feature comparison, the partner that leverages Copilot will give you better software and better support for your money.” - Marcel Chabot - Development Manager at The TM Group, Inc. Are you using this criteria when shopping for a new vendor? Hit the link in the comments if you’d like to see the full 34min interview with Marcel. Dynamics Compass #copilot #github #msdynamics #microsoftdynamics #mspartners

4

1 Comment

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

3 things I wish someone told me about software delivery. 1. It has nothing to with Canada Post. Or any other postal service. 2. Releasing software generally doesn't feel anything like that scene in Free Willy of the killer whale leaping out of the water over the storm barrier. 3. Developing and delivering software is really hard - so I'm still not sure why it's called "software" and not "hardware". [photo: Blacks Rapids lock, Rideau River, Ottawa] — I'm Russell 🐿️. A long time engineer discovering new life as a first-time solopreneur. #devops #continuousdelivery #softwaredevelopment #testdrivendevelopment #platformengineering

4

1 Comment

There is a $7.5B company that: • Started with $0 funding • Has 100M+ active users • Generates $1B+ in ARR And now powering the open-source revolution. Here’s the story of GitHub: Tom and Chris were both working at CNET when they met in the mid-2000s. They were both passionate about software development and knew that developers needed better tools to manage and share code. In 2008, they started working on a side project that would change their lives. Git was a version control system at the time. But it had terrible UI and no functionality for collaboration. Their idea: build a web-based platform to host the Git repository. It would revolutionize the way developers collaborated on code. They launched GitHub in April 2008 with just a handful of users. Early on, they bootstrapped with an intense focus on customer experience and on exceptional UI. And they fully embraced the open-source community. The commitment paid off... Three years later, they had over a million developers on their platform. GitHub became the focal point of the open-source revolution. Hosting and collaborating on code was never so easy. Even big tech (FB, MSFT, Google etc) became customers. From there things skyrocketed 👇 By 2012, the biggest VCs started noticing. GitHub raised $100 million in Series A funding led by Andreessen Horowitz Their growth was explosive. By 2015, they had 9 million users and hosted over 21 million repositories. How did they scale so rapidly with a relatively small team? Simple answer: They leveraged talent all over the world. GitHub adopted a distributed team model early on, hiring talented developers from around the world. Scott Chacon, a co-founder, worked remotely from Mexico, setting the precedent for a global workforce. GitHub attracted top talent from regions like Eastern Europe etc. GitHub's distributed model also allowed for continuous development cycles with teams in different time zones. By 2018, GitHub had revolutionized the developer experience. And Microsoft bought them for $7.5 BILLION. All the co-founders are billionaires. Not bad for a side project. GitHub, WhatsApp, Wayfair and many giants were built on global talent. Trained pros take on rote execution at a fraction of the cost, while top teams focus on strategy and product. GrowthAssistant embeds elite, college-educated pros from the Philippines directly on your team. We find and place talent with the EXACT skillset you need. DoorDash, HubSpot, True Classic, and 200+ others use us Check it out:

23

2 Comments

💥 Two years after Tim Horton’s settled a class action in Canada for sharing location data through its use of the Radar SDK in its app… 💥…And two years after Greenley vs. Kochava claimed the Kochava SDK intercepts consumers’ location data when using mobile apps 💥…Bender vs. Twilio claims the Segment SDK collects personal information in a similar fashion. Are class action plaintiffs taking up the cause of SDK liability? Or are these flukes? In Bender vs. Twilio, Noah Bender downloaded and used the Calm meditation app on his cell phone. He later claimed the Segment SDK intercepted sensitive communications between himself and Calm. Segment is designed for developers to collect data , including search terms, search results, keystrokes, button presses, page views, and consumers’ names and email addresses. Bender is suing Twilio for violating America's Wiretap Act, the California Wiretap Act, and California's Comprehensive Computer Data Access and Fraud Act (CDAFA). This may be the Calm before the storm for class actions. Bender's complaint alleges over 11,000 app developers have integrated Segment into apps for shopping, productivity, gaming, and mental health. With Boltive, companies find litigation risks in their iOS and Android apps before plaintiffs do #privacycompliance #dataprotection #dataprivacy

66

13 Comments

Some tips if you are working in a startup (as a backend engineer): #1. Keep logic away from the DB -- Avoid triggers and stored procedures. -- Put all application logic in your server. Simple constraints like primary key, and NOT NULL are fine to have in the database. Complex validations (Users can comment once in three minutes) should be in the app. #2. Don't delete data -- How do you delete a user? Set the status as deleted. -- How do you update an invoice? Insert a fresh record. Keeping old records helps debug systems. Don't overwrite stuff that you will need later. A fresh insertion is better. #3. Logging is not a substitute for testing I see codebases where everything is logged. It's a symptom of poor testing. "Request {object} received" "Processing {object}" "Cache miss." "DB {query}" "DB {response}" "Response {object} cached." "Response sent {object}" You don't need to log so much. Engineers can see how their code behaves and infer what went wrong (as long as the request path is obvious). Instead, just log these lines: "Request {object} received" "Response sent {object}" It's enough to know what happened. If you get an exception, log that instead of the response. #4. Know (enough) about your libraries If you are using a framework or library, it's good to know a little about how it works internally. You needn't be an expert at it. Learn with a "Need-to-know-basis" :p ------- If you want to deep-dive into the internals of distributed systems, try the system design course at InterviewReady (Good for SDE-I to Staff Engg). All the best! #SoftwareEngineering #BestPractices #Startups

2,239

117 Comments

Earlier this year, I interviewed at the three biggest QA Contract companies. The position? Working on new AI driven QA programs... We are about 6 months out from when most of those programs will be shown to the major AAA game companies they work with. I'll say it before, and I'll say it again. If you want to continue to be in QA and work for AAA companies, you best be doing all you can to show your worth in regard to AI. Period. If you dont, things will get bad real quick... Also, I understand.. Unions.. Unions can also disappear real quick when that organization is no longer needed at the company.. You've been warned for awhile... Dont be too shocked when things go south for you and you just sit back hoping it doesn't. If you know AI/ML... You can be shown value elsewhere in the company once the first dominos fall... #qa #gaming #ai #ml

3

1 Comment

One simple way to retain software engineers. An end of year review. Goal setting for 2025. Proper 1-2-1 time. Where possible, ideally face-to-face. Sounds obvious. But many engineers I speak say it doesn’t happen. People want to feel valued. When was the last time you had a 1-2-1? #retention #endofyearreview #2025goals

8

Feeling lost in the sea of no-code/ low-code tools? I’ve been there! After trying to find a single "magic tool" that could handle everything—from building versatile software to managing complex integrations—I realized there’s a better way. Here’s what worked for me: Instead of relying on one tool to do it all, I found that using ChatGPT as a guide made all the difference. My custom assistant now helps me map out each project step-by-step, directing me to the best AI, automation, or no-code tool for each specific task. ChatGPT even generates ready-to-use code for each step. One key insight: don't prompt. ChatGPT understands intent communicated through human language better than it understands scripts, so explaining your project as if you’re talking to a colleague yields better results. If you’re exploring no-code or low-code solutions, this approach could save you countless hours of trial and error. Happy to elaborate further if anyone needs help to get moving.

7

We've hired 200+ developers since we started Trio. There are 3 crucial skills we look for in every new hire (other than their developing skills): → 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻 - As a remote-first company, clear communication is non-negotiable. You need to be able to convey technical concepts and get your point across plainly through emails, messages, and video calls. No room for guesswork or assumptions. → 𝗔𝗱𝗮𝗽𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆 - Things are always changing in the tech world, and we need to keep up. We need reliable team members who can adapt to our evolving projects and priorities. → 𝗖𝗼𝗺𝗺𝗶𝘁𝗺𝗲𝗻𝘁 𝘁𝗼 𝗘𝘅𝗰𝗲𝗹𝗹𝗲𝗻𝗰𝗲 - Our top talent takes pride in perfecting their craft and driving innovation. Mediocrity is not in their vocabulary - they will go above and beyond to wow our clients and push the boundaries of what's possible. What matters MOST is finding team members who share our passion for continuous learning, problem-solving, and desire to create innovative solutions that make a real impact. What about you? What do you think is most important when hiring great talent?

72

2 Comments

Embrace uncertainty, become comfortable with change... The software space has arguably changed more in the last 2 years than in the last 20. Change is never comfortable, but that's where growth happens: #SoftwareEngineering #Change #Growth

20

Generative AI in Software Development: A Double-Edged Sword 🌍 Generative AI is transforming the way we develop software, bringing both significant advantages and challenges. As AI tools like GitHub Copilot and others continue to evolve, here’s a quick breakdown of what we gain and what we need to watch out for: Pros: ✅ Increased Speed & Efficiency: AI can help developers write code faster, reduce repetitive tasks, and automate debugging, allowing teams to deliver software more quickly. ✅ Better Code Quality: With AI-assisted code reviews and bug detection, developers can identify and fix issues earlier, improving the overall quality of the product. ✅ Smarter Testing: AI tools can automatically generate test cases, spot edge cases, and speed up quality assurance, leading to more reliable and bug-free software. ✅ Empowering Non-Developers: Low-code/no-code platforms, powered by AI, are enabling non-technical professionals to create applications, democratizing development and fostering innovation. Cons: ❌ Over-Reliance on AI: Heavy dependence on AI tools may reduce the need for developers to engage deeply with the code, potentially weakening coding skills over time. ❌ AI Bias & Ethical Concerns: AI-generated code might inadvertently reinforce biases or ethical issues. Developers must remain vigilant in ensuring fairness and security. ❌ Potential Job Displacement: While AI increases productivity, it could also reduce the need for certain types of development roles, especially in routine coding and testing tasks. ❌ Learning Curve: Integrating AI into the development process requires upskilling, and not all developers may be comfortable with the new tools. ❌ Quality Control: AI-generated code isn’t always flawless. Continuous oversight is necessary to maintain high standards and prevent hidden issues from slipping through. Generative AI holds immense potential to enhance software development processes, but it’s crucial for organizations and developers to use it thoughtfully—balancing automation with human expertise to ensure quality, security, and ethical standards.   #GenerativeAI #AIInSoftwareDevelopment #TechInnovation #AIDrivenDevelopment #MachineLearning #SoftwareQuality #FutureOfWork #AIethics #LowCode #NoCode #AutomationInTech #DevOps #ProductivityInTech

2

Here’s what I see. I see companies like Workato and TRAY.IO INC. being sold as integration middlemen because custom integration is so wildly expensive. The top brass is being told that custom will cost a $ million and 8 months, or the middlemen will only cost $500k and 4 months and they jump on a bad comparison because the numbers are so high. Squillo‘s micro-middleware is better, faster, cheaper and actually works. Time to start putting the 🪓 to the middle.

6

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

Too many times, I have found myself discussing team structures and hiring strategies in my career. Should we hire full-stack people or strong specialists? From my experience, there is no silver bullet, so both directions can form strong teams, but we need to acknowledge that both strategies have pros and cons. One extremely costly obstacle to the team's success, though, is when tech professionals struggle to understand the user's journey holistically due to limitations in their tech knowledge and skillset. Modern web applications are quite demanding beasts since they tend to pay huge attention to User Experience, of course, for very good reasons. This is exactly where things tend to go south because a seamless and intuitive User Experience is usually accomplished by combining a heck of things and technologies. Tech people who are not limited by their hard skills are the ones who can see the whole picture, understand the application's high goals, work closely with business stakeholders, and ultimately can even guide the business people into delivering something useful. Why? Because they can see the whole map from the top of the tower and not from the first floor. It is a matter of perspective to be able to see the whole puzzle and grasp how various pieces fit together. Don't let your hard skills limits prevent you from becoming such an impactful tech professional 😉 https://lnkd.in/dsxD9Gbj #webdevelopment #careerdevelopment #software #leadership #management #engineering

18

1 Comment

*Bracing myself for the response I might get for asking this* Software Engineers: Would you ever consider working on an EQUITY ONLY basis (ie no salary, just owning a portion of the business, the value of which would increase as it progresses and scales)? Assuming: - The product is really interesting and so is the work - The product is in the "tech for good" space and would be a really positive contribution to parts of society - Seed funding is confirmed to be coming with several backers keen & they will able to offer a salary in the near future - The product is super early stage, you would be writing the software from the ground up, but the concept, design and business model once funding is received are all solid I know that there will be many who would never consider this under any circumstances and I totally get why, but just curious to hear if any of you would if it was for a product you believed in enough? And would you look at it on a full-time basis or a part-time basis? It's something I got asked about and so I thought I would throw it out to Linkedin to see what you all think rather than assuming that I know the answer on your behalf. #startup #founder #softwareengineer

39

309 Comments

What makes a product go viral? In the case of ChatGPT, a great product + strong partnerships. The ChatGPT product team has certainly done a great job with the product. With its simple UI, it feels like magic is just a click away; there's no need for complicated coding, joining Discord channels, or anything else. Simply open a browser and explore it. Many people say this is the type of product that goes viral on its own. For the most part, I agree. OpenAI doesn't have a large marketing team, nor does it run major campaigns or demos to push the product to millions of users. OAI also leveraged a phenomenon I call FLG "Funding Led Growth". Akin to a prize fight, the larger the purse, the more people watch, the larger the purse becomes, and so on. The sheer size of the investment used to build OAI and ChatGPT created a gravitational force that tugged on users and media alike. But if you examine their growth, you'll notice a critical factor: their partnership strategy, especially with Microsoft. Here's what Microsoft brings to the table. → 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻 Microsoft's extensive enterprise connections and the vast network of companies using its Azure platform give OpenAI an advantage they wouldn't have otherwise. By integrating OpenAI into Azure, the platform becomes the easiest choice for developing custom AI models, exposing OpenAI to a massive customer base. Azure has penetration with ~ 95% of Fortune 500, has over 145M daily active users on Microsoft Teams, and over 250K companies using Microsoft Dynamics 365 and Microsoft Power Platform, according to Microsoft. That's a lot of B2B/enterprise customers that OpenAI has a head start with. → 𝗡𝗲𝘁𝘄𝗼𝗿𝗸 𝗘𝗳𝗳𝗲𝗰𝘁 The growth of AI relies on network effects, but not in the traditional way seen with technologies like telephones where more users directly mean more connections. Here, the more users that engage, the more data is available to train the AI, making it smarter and more attractive to new users. (this is potentially a drawback or cause for concern for enterprise users which OAI needs to overcome) When we first tested ChatGPT, its responses were impressively human-like. However, it was restricted to data up to 2021 —making it outdated for recent inquiries. OpenAI's partnership with Microsoft provides a method to improve that. User interactions on Bing serve as both a testing ground and a source of real-time data, allowing ChatGPT to constantly evolve and enhance its capabilities. So the takeaway is simple: create a great product first, use this product as a wedge to attract customers and forge strong partnerships, leverage this partnership to bring more customers on a large scale (AND improve the product). Both things are important but need to be in order. Below is an image from Jaryd Hermann's article, "How OpenAI Grows." In the bottom left, you can see how Microsoft's distribution and resources have been pivotal in fueling ChatGPT's growth. Thoughts?

72

24 Comments