A N M Bazlur Rahman

TorontoJS — thanks for having me give a talk on React TypeScript Patterns at yesterday's JavaScript Tech Talk event! Huge shout-out to Snowflake for providing the venue, Alex Okrushko for hosting, and all the organizers from TorontoJS. Such a great event — already looking forward to the next tech talk! #reactjs #typescript #javascript

174

7 Comments

As a #StaffEngineer, part of your role is going to be helping maintain your #TestSuite. Two questions for you: 1) If your test suite is green, can you push to prod RIGHT NOW with a high degree of confidence that nothing will explode? 2) If your test suite is red after running your e2e tests ONLY ONCE APIECE, do you have a high degree of certainty that something is actually wrong? If your answer to either of these questions is anything but an immediate "yes," your test suite isn't doing its job! Wanna hear more? Of course you do! Come hear me speak on maintaining a solid test suite on May 14 in Raleigh! Buy tickets here: https://lnkd.in/endei_Q3 Pictured below: An engineer stressing out over the "only once apiece" bit up there. Yes, it really is achievable!

4

2 Comments

When you need to source software engineers quickly ProgAI can help. Not just a list of candidates to present to your hiring manager, but candidates with the skills that match the role and will likely move. Our Likely-to-Move™ Score helps you know this. This smart feature predicts how likely a software engineer is to switch jobs, based on over 20 different market signals. You get to target the right candidates. You are no longer For HR teams... They can spot engineers likely to leave their roles and take action to keep their best performers on board. Ready to see how it works?

4

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

Last Call! 📣 🚂 We're gearing up for our next Observability Engineering Community London meetup, which is happening this Wednesday! This time, we've got two great talks by Dinesh Nithyanandam, Lead for Observability, Performance, and Reliability at A.P. Moller - Maersk, and Carly Richmond, Principal Developer Advocate & Manager at Elastic. 👉 Dinesh will discuss how A.P. Moller - Maersk leverages Flagger to automate canary deployments across its extensive infrastructure, which includes 120 clusters and over 1,000 microservices running in a multi-cloud environment with AKS and GKE. By integrating with monitoring tools like Prometheus, Flagger continuously evaluates key SLOs, ensuring that new versions are only fully deployed if they meet defined reliability and performance standards. 👉 Carly will draw on her experience in building applications for investment banking to explore why validating long-term feedback on feature adoption is challenging. She will discuss how combining Real User Monitoring agents, such as Elastic RUM, with OpenTelemetry tracing for backend services and Elastic Observability can help quantify user experience satisfaction and adoption, ensuring effective user experiences. 📅 Event Details: Date: Wednesday, September 11th Time: 6:00 PM Location: 24 High Holborn · London See you all there! #Observability #Engineering #SRE #SLO #devops

4

Something you can’t do with Shopify flows’s native actions to make api calls is do anything with the response that you receive. Thats what this action in flow helper is for.

19

🚀 Modularization in iOS isn’t just about organizing code—it’s about building apps that scale seamlessly. But here’s the real question: Horizontal vs. Vertical modularization—which approach makes your code better? 🔹 Horizontal Modularization: Think of it as organizing by responsibility (Networking, Persistence, UI). It’s great for reusability across features but can lead to tight coupling if not managed well. 🔸 Vertical Modularization: Feature-first! Each feature (Login, Profile) becomes a self-contained module, perfect for independent development. But watch out for duplicated logic. 👉 The Sweet Spot? A hybrid approach: horizontal for shared infrastructure, vertical for features. This combination keeps your code clean, scalable, and ready for growth. How do you modularize your iOS projects? 💬 #iOSDevelopment #CleanCode #ModularArchitecture #Swift

3

Observation: 9/10 SWE's quit at “reading the docs”. Cut through the BS with this easy trick: Take action and build. Writing code is 100x easier than the docs make it sound. “Reading the docs” gave me crazy imposter syndrome: -Git -WPF -Kafka -OAuth -Angular -GraphQL -RabbitMQ -Kubernetes In ALL cases, I conquered my fears by building. Except for WPF. I gave up on that. And Kafka, that's for another day. Forcing yourself to build/code/deploy melts analysis paralysis. Then you'll say "oh that was pretty easy". Trust me, we aren't building rockets. Practice AND Study build true mastery.

22

1 Comment

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

What are some of the biggest myths about quality assurance? Want to know how to streamline GraphQL service testing? Can you use a no-code approach to help with performance testing Find out in this episode of the Test Guild New Shows for the week of July 14. So, grab your favorite cup of coffee or tea, and let's do this.   Featuring automation awesomeness contributions from: Vitaly Sharovatov Qase Jason Arbon trivago Armin Aminian Giuseppe Donati Karate Labs Chris Rolls Stephane Landelle Shaun B. Gatling Venue.sh Tracebit and more!    ** ALL LINKS W/TIMESTAMPS IN THE FIRST COMMENT BELOW ** #devsecops #automationtesting #softwaretesting #performancetesting

55

14 Comments

Most companies struggle to hire killer senior engineers. So what should the ideal interview process for finding this talent look like? Whenever I advise early-stage tech startups, I tell them to include the following questions and steps in their interview process for senior engineers: 1. Have them interact with stakeholders in the company You need proof that a senior engineer can work well with stakeholders. They must be able to delegate and empower engineers to make various decisions. Any engineer who can communicate well and work with stakeholders is a solid hire. 2. Have them speak to a designer or product manager Senior engineers will be speaking to designers and product managers frequently. If you can get a designer or product manager involved in the interview process, you want your colleague to assess whether that engineer is someone they can work with. Some questions they can think about include: - Can I have a conversation about what’s valuable to the business with this engineer? - Can this engineer communicate well? Do they complicate things? Do they oversimplify? - How do they react if there’s an ask from design or marketing? What is their thought process? 3. Figure out their attitude toward junior engineers A senior engineer’s attitude toward junior engineers is a good bellwether of their attitude toward communication and documentation. One sign of a poor senior engineer is someone who can’t explain their work — or doesn’t feel like they have to. They feel no need to document what they’re doing and they assume everyone around them, like their junior engineers, will just get it. If you ask an engineer, “How do you communicate your work to others?”, and they say “I don’t really see the value in that,” that’s not someone you want to hire. It’s incredibly important to an early-stage organization to prioritize clear documentation and communication. I’ve advised too many companies that did this too late and had to waste time parsing the code of engineers who didn’t bother to document anything. Any startup can avoid this fate by hiring good senior engineers who explain their work every step of the way. 4. Figure out how they plan for the future Developing a good product isn’t just about good design or code. It’s also about future-proofing your code. I think a big thing about seniority is balancing making good decisions quickly while not shooting yourself in the foot. It means seeing beyond the future and recognizing the implications of their decisions, such as: - Is this code future-proofed or not? Am I creating technical debt? - Has this particular solution created any new problems for the team? Who knows how to solve them? Am I the only one who knows? You especially don’t want your company to deal with technical problems that can only be solved and documented by one person on the team. That can lead to a crisis if that person ends up leaving. cont. 👇

3

1 Comment

Do you know that 𝘼𝙣𝙙𝙧𝙤𝙞𝙙 𝙎𝙩𝙪𝙙𝙞𝙤 provides the option to 𝙚𝙭𝙥𝙤𝙧𝙩 your project as a 𝙕𝙞𝙥 file? 🤐 When you want to share the project as a Zip, you have to delete the 𝙗𝙪𝙞𝙡𝙙 folder as there are generated and SDK files which we don't need. When I use to ZIP my project, I use to delete those and then Zip 😁 but Muhammad Atif gave me the idea of exporting it as Zip. Thanks Muhammad Atif for the tip.

175

14 Comments

💎 What's better than a spring day? A spring day where you learn how to avoid using JavaScript in Ruby on Rails apps. If you're in Montreal, I'll be giving a talk tomorrow at 6pm on Ruby Hotwire: Drive, Frames, and Streams tomorrow at Potloc. https://lnkd.in/emc9KrM8 #RubyOnRails #Hotwire #NoJavaScript #WebDevelopment #TechTalk #MontrealTech #RailsDevelopers #RubyHotwire #SoftwareDevelopment #CodingTips

6

Need help getting your startup idea off the ground then get in touch with these guys. They were able to help me at short notice. UX through to software dev.

2

System design isn't a Cut & Paste job. Scalability is a frequent hurdle. But how to handle it? You can address the scalability problem from the point of view of the Read/Write Ratio.  • Step 1: Separate services so they can scale differently. • Step 2: Add a cache layer. • Step 3: Improve performance at the storage level, separating reading from writing. Systems design is 90% about understanding the problem at hand, not copying solutions. Here is the whole article 👇 https://lnkd.in/ePkqPWnX

191

38 Comments

After React Native and Flutter, Kotlin Multiplatform (KMP)is going to be a good option in crossplatform mobile development. Especially KMP is based on Jetpack Compose, that means the Android developers who are familiar with Jetpack Compose can adapt to KMP much easier. #reactnative #flutter #kmp #jetpackcompose #crossplatform #mobiledevelopment

13