Brett Allred

I've made a change to my blog's stack, I've transitioned from Blazor to React. Although I know Emiliano Montesdeoca del Puerto won't like this change.😎 I've also documented the process of publishing a React page using GitHub Pages workflows. Check out my latest blog post to learn more: blog.pablosr.com/post/10 #React #Blazor #GitHubPages #WebDevelopment #BlogUpdate

11

1 comentario

💡 Lead your remote/distributed teams with empathy (my own experience): Working with remote or distributed teams can be a challenge for Engineering Managers. Keeping your teammates aligned across different time zones, countries, or cultures requires excellent organization, best practices, and a lot of emotional intelligence. One thing I’ve learned is that beyond technology and processes, the human factor is probably the most important to manage. You’ll need to resolve conflicts, build trust, and boost productivity, but you won’t be able to do it without empathy—I can assure you of that. A few quick practices that have helped me are: ▶ Clear goals: Ensure everyone is following the same direction. Keep the goals visible to the team (e.g., JIRA board, Slack, etc.), and provide friendly reminders if you have stand-ups with them. ▶ Good communication and cadence: Schedule regular check-ins. Make sure the team feels heard. ▶ Flexibility and cultural differences: Be flexible with schedules and learn how to communicate with different cultures, as not everyone works in the same way. Practice deep listening with your teammates and set clear expectations. Learn what is "normal" for them and find a balance to create a good fit within your team. ▶ Foster a safe environment: Create open discussion spaces for the whole team, plus 1:1 meetings. A meeting I’ve been using a lot, which often gets overlooked, is the retrospective. But for your team to participate and share their true feelings, they need to feel comfortable. What has been your experience leading distributed teams? I’d love to hear other points of view, thoughts, and reflections! Remember, I’m creating more content related to engineering management at https://daniheredia.com/ So sharing it is always more than welcome 🙇‍♂️ #leadership #engineeringManager #remoteTeams #empathy #distributedTeams #distributedTeams #emotionalIntelligence #diversity #cultures #newsletter #team #teamWork

12

Announcement: We are rolling out our nearshore offering to startups and medium-sized companies 🎉 Reach out to learn how you can achieve your software engineer goals without breaking the bank. #softwareengineering #nearshore #softwareengineering #react #javascript

6

We work with some amazing customers. Some I’ve had the opportunity to work with for close to 5 years and have built incredible partnerships with. GitLab Loadsure Arrive Logistics thanks ! But in 2024 things are shifting in a way lately that have made me feel uneasy and led to this post. IT Nearshore Etiquette 101: Here are 10 non ideal things I see happening in the tech nearshore/outsourcing space that need to improve. 1. Treating nearshore services as disposable assets for tech projects. Once it doesn’t work out, whole teams are obliterated without a second thought. It’s not about keeping work that you don’t need, it’s about reasonably bundling your in-house hiring practices/policies into your nearshore hiring practices 2. Imposing a nonfunctional culture or pod structures on your new team. If that worked, you wouldn’t have opted for nearshore to begin with. 3. Hiring requirements that must include: full stack in all technologies, project management experience, in office, protector of the realm with at least 57 years of experience. Oh yeah, great soft skills too. Multi-threading here sucks. 4. Starting the conversation with: I have the lowest budget possible but this is a key initiative for the company (great…). Customers that value quality within their teams are more successful. 5. Opening up 20 requisitions, conducting 20 high-quality interviews after 20 days’ worth of work, and changing requirements to only 1 open position last minute. Understanding that both sides must actively participate in the hiring process with timelines, risks and visibility is key. 6. Leaving your nearshore team out of all company communications. Cohesion in a team is so important. Your teams are your teams, no matter where they are. 7. Calling your nearshore team contractors directly when trying to have a cohesive culture amongst your tech team. Just another way to create a gap in your team culture. 8. Giving your dev team a partial vision and restricting their ownership of the product to the next line of code they write. Engineers play a vital role in the creation of new initiatives, from its inception / ideation point, not just software development 9. Having zero onboarding plans for your new team and expecting everyone to be up to speed within the first month. 10. Not working with Lean Solutions Group’s Tech División, Lean Tech to help sort all of this out with technology, single-digit attrition, amazing culture, and off-the-charts productivity. I am actively invested in democratizing access to the incredible LATAM talent across the globe and ensuring that these best practices are enforced is part of that. Might not be pretty but it’s a path forward towards streamlining IT nearshore practices and making it an incredible experience for all. Teams that have these items buttoned up, win. Thank you for reading

39

Interesting to see NTQR in action. #AI #Python #NTQR

2

There is no doubt in this fact considering the better features we have experienced when using Playwright like async awaits, no promises, checks retry, better debug, single API, complement dev workflows, using websocket protocol for faster execution, browser context for isolated test execution, supports cross domain like in case of SSO redirection, parallel execution...

5

Considering outsourcing a software development project? Here are five tips for finding a good service provider. 1. Take a good look at near shoring firms based in Mexico, central or South America. There are some really good options out there that are economical, close in time zones, culturally similar to us in the US 2. Find vendors that have done projects similar to yours. Especially if you are in a regulated industry like fintech or healthcare. You don’t want them learning this stuff for the first time on your project 3. It can be really enlightening to talk to your prospective service provider’s past clients. Ask about velocity, quality, language abilities, accountability, responsiveness and if they went above and beyond for them 4. Gather feedback systematically using a spreadsheet. Remember, it’s not just about cost when comparing vendors. 5. Finally, reach out to your network or to find where people have had positive engagements with service providers What are your tips for finding great software development service providers? Please share your experiences in the comments below #entrepreneurship #mvp #outsourcing

15

3 comentarios

Can someone explain to me how to get "more experience"? I have 16 years of full stack software engineering experience, mostly in C# .Net 4.2 through 8, including .Net Core 2.x & 3.x, along with WCF, WPF, Winforms, Razor/Blazor, HTML, CSS, and JavaScript, with Entity Framework, Dapper, Linq, SQL Server, MySQL, SQLite, Oracle, NoSql, and other databases. And a few of those years include a combination of Java, PHP, and C/C++. I've also used MarkDown, PowerShell, MVC framework, Swashbuckle/Swagger, Newtonsoft, JSON .Net, TopShelf, and a variety of testing frameworks. But apparently that's not enough. In the past 3 years alone, I've learned ReactJS, TypeScript, Xamarin, XAML, Maui, NodeJS, Terraform, AWS, and Azure, and I'm currently learning Angular, but that doesn't cover the 3-5 years of experience jobs want. I've learned some of these skills through jobs, but also some on my own. Except that as often as companies want us to learn these skills outside of work, they only count professional experience when it comes to hiring. My last interview said I needed more experience, as if the previously mentioned 16 years wasn't enough, and neither was the 15 years of computer repair and networking before that, which their interview questions also covered. So if no one is willing to hire because people don't already have experience, how are we supposed to get the experience? And don't say "open source projects", because they don't count as professional experience. Or do I have to take a 50% pay cut to take an "entry level" job that still requires 3-5 years of experience that I somehow still don't have? People are quick to say that "no one wants to work anymore" when they can't get hired, but they never seem to think "businesses aren't willing to teach anymore" when they refuse to hire people. Why? Is it that we are so conditioned to think that it's always the individuals fault for not living up to expectations, instead of the businesses fault for setting unrealistic and ever changing expectations? So, I ask again, how can I get the required experience when employers refuse to hire unless I already have experience?

2

Want to learn how to pace the start of never-ending concurrent effects? https://lnkd.in/ecWBEKZt Rodrigo Germán Molina shares his tips in our latest blog article 👀 #CatsEffect #ScalaProgramming #FunctionalProgramming #ConcurrencyControl #SoftwareEngineering #DistributedSystems #PerformanceOptimization #TechBlog

9

Feeling like your software development is stuck in first gear? It's time to turbo-charge your project with nearshore tech. Imagine slashing development time without sacrificing quality. How? By leveraging a dedicated team of skilled professionals in your time zone. No more delays. No more miscommunication. Ready to put the pedal to the metal? Let's accelerate your software development with nearshore tech. Hit the gas. Let's get started. 🚀

153

12 comentarios

I'm GitOps at Scale with Argo Certified from Codefresh, 🎉🥳 and CodeFresh’s learning materials are really great, especially for getting into Argo CD and GitOps concepts. Check them out. #Kodez #CodeFresh #OctopusDeploy #GitOps #ArgoCD

40

10 comentarios

A lot of times that I talk to highly experienced technical people about how to start a new software business, they want to discuss what tech stack to use on the project and what architecture it needs. That's putting the cart before the horse. That's thinking that when starting a new business, the uncertainty is about the technology. But it isn't. The most uncertain thing that you should focus when starting a business is if there is a business at all, if there is anyone that would pay for your product. The technology has to help the business to reduce its uncertainties in the most fast and effective way possible, and in order to do that you need to reduce its complexity. Simple architecture, simple infrastructure and simple deployment. You just need to use a monolith, with a boring and tested framework (I use Ruby on Rails, BTW). There is always time to scale later. Scaling is always a good problem to have, because most of the time you won't need it, as there wasn't any business there.

21

1 comentario

A few weeks ago, I wrote a Twitter thread about technical debt, inspired by a conversation at the Open Space event of the Barcelona Software Crafters. It was there that I realized just how differently people interpret this concept. Some stick to the original idea, others have their interpretations, and some even coin new terms to better describe what they believe the concept should represent. That thread sparked something bigger: the need to dive deeper. While Twitter is great for quick takes, it’s far from the ideal medium for a nuanced discussion. That’s why I decided to publish my first Substack article. In this article, I explore: 👉 The origins of "technical debt", start with Ward Cunningham’s metaphor. 👉 Diverse perspectives on the term, drawing from experts like Kent Beck, Martin Fowler, Michael Feathers, and others. 👉 Different paths teams take when managing technical debt: 👉 The happy path, where debt is addressed in the same development cycle, prevents it from growing into unmanageable "interest." 👉 The sad paths, range from short-term debt repayment to catastrophic scenarios where unresolved debt sinks entire companies. 👉 Actionable solutions and mitigation strategies, as presented by authors and researchers who have dedicated decades to studying this topic. This article wouldn’t be possible without the invaluable insights shared on their books, articles, and videos of: - Ward Cunningham - Kent Beck - Martin Fowler - Michael Feathers - Dave Farley - Adam Tornhill - Kevlin Henney - Andrew Brown - Mary & Tom Poppendieck - Luis Artola - Fran Iglesias Gómez - Bob Salmon I’m incredibly grateful for the work of these authors, and I’ve included many of their words and ideas to ensure this article offers valuable, well-researched content. If you’re curious about what technical debt means, how it impacts businesses, and strategies to manage it, I’d love for you to check out the article. Whether you're a developer, team lead, or just someone intrigued by software crafters, I hope you find it insightful. 👉 https://lnkd.in/d9M37t53 Finally, I want to extend my heartfelt gratitude to Ricardo Guzmán Velasco, Fernando del Caz Babón, Manuel Rivero (TrikTrok), Javier Lopez Fernández, and Iván Moreno García-Fresneda for their invaluable support, thoughtful feedback, and insightful inputs that significantly enriched this article. Your guidance, encouragement, and perspectives have been instrumental in shaping this work. I also want to thank everyone who took the time to share their thoughts and provide feedback, your contributions have made a meaningful impact. #TechnicalDebt #SoftwareCraftsmanship #Refactoring #Agile #ContinuousImprovement #SoftwareDevelopment #CleanCode #LeanSoftware #TeamCulture

36

2 comentarios

Maximize your development efficiency with nearshoring! Scaling your development teams doesn't have to be a daunting task. Nearshoring offers a streamlined solution that maximizes efficiency and productivity. Here’s how: Time Zone Alignment: Nearshore teams operate in similar time zones, enabling real-time collaboration and faster decision-making. Reduced Overhead: Nearshoring eliminates the need for extensive infrastructure investments, reducing overhead costs. Expertise and Innovation: Access to a broad talent pool brings diverse expertise and innovative solutions to your projects. Risk Mitigation: With SHORE teams, you benefit from our rigorous vetting process, ensuring you work with reliable and skilled developers. We’ve seen firsthand how nearshoring can drive success for our clients, providing the agility needed to navigate today’s dynamic business environment. Enhance your development operations with nearshoring. Contact us to get started! #nearshoring #efficiency #softwaredevelopment #innovation #globaltalent

54

11 comentarios

🔥 New episode of The Headcount People drops TOMORROW 🔥 In Episode 12, I have a conversation with my friend Alisa Avelar, the former VP People at Docker, Inc, Modo Labs, and Toptal. I have to say, Alisa strikes the perfect tone in this pod: speaking both to the head and to the heart. Her ability to drive strategic value and outcomes to the C-suite PLUS serve as a trusted resource to employees is what makes her such a dynamic HR leader. Whether you're an experienced HR exec or aspiring to lead a People function one day, this podcast will be a great listen. Here is just a short snippet of what Alisa has to share – and be sure to check back tomorrow for the full pod! #podcast #peopleleadership #hrleadership #theheadcountpeople

8

1 comentario

Another great reason to update your React Native codebase to use Expo SDK 52 - Expo Video is finally stable 🎥 🚀 When you migrate from Expo AV, you’ll enjoy picture-in-picture mode, background playback, and more ✨ (need a hand with codebase maintenance or upgrades? my DMs are open 😉) #reactnative #expo https://lnkd.in/gTdfQauZ

2

Wrote a post on Dev.to about troubleshooting WalletConnect WebSocket connection issues. If you’re dealing with wss://relay.walletconnect.org failures, this might help! Read more here: https://lnkd.in/dR4hnk9T #Web3 #WalletConnect #Blockchain #DeveloperTips

3