Michael Moura 🇧🇷🇺🇸

so what is your move gaes

1

Jr. Devs, You need to start thinking outside the box when it comes to your career. I was talking to a friend of mine yesterday and they were telling me about a small business their children (12 and under) had started. I won’t reveal what it is to protect their small advantage. :) But basically, it's providing a simple service that takes very little time for very little cost. It's offering a convenience. Anyway, as he was telling me about it, it was so simple, so obvious, but something I would have never thought of on my own. I’m not really an idea person. I need something to start with, a clear problem to solve. I often need a pre-defined path to follow. Many Jr. Devs need to be less like me, trying to follow the pre-defined path, and more like my friend, looking for things other people might be missing, opportunities no one may notice. Think about ways you could implement what you are learning to help individuals, small businesses, local governments… virtually anyone; to fix a problem, meet a need, or simply make someone’s life easier in areas they may not have thought of themselves. The traditional route into development is clogged right now, so perhaps it’s time to look around and see opportunities from a different perspective. Find a non-traditional route to begin using your skills in a career that might look a little different from everyone else. Who knows, you just might stumble on the next Uber or Airbnb or maybe you just build a great list of clients who need simple work from a trustworthy developer. Take a fresh look at the problem and find a creative solution. #juniordeveloper #mentoring

14

1 Comment

Accessibility Tip of the Day 271: Here's a great (and short!) article from Adrian Roselli on "Things to do before asking 'Is this accessible?'" (https://lnkd.in/gK7E5wRa) The big three questions he typically asks in response are: 1. What do you mean by "accessible"? 2. What prompted you to ask that question? 3. What work have you already done to check? #accessibility #a11y #accessibilityTipOfTheDay

11

2 Comments

If you struggle with networking - just meet people that work on the same thing as you, but at different companies. Grab virtual coffee to compare notes casually. You can find them on social media, communities dedicated to your field, tech conferences, and other places. Just compare notes + help/be helped + make a friend. Do this a lot. You'll help your current employer with added perspective on a problem space. You'll help yourself by making a new friend! We need to stop defining "colleague" as "works at the same company" but rather someone we just collaborate with professionally in any capacity

116

8 Comments

Y'all, I implemented authentication my first time solo!!! 🎆 I think anyway... 🤔 (Maybe I have in a JS-only app before, but this was React & TypeScript.) Auth was *the* thing I wanted to do today. I took the time to break my next steps in this app into little issues. Although this first, was quite large. I wanted to do it via the Firebase docs alone and, admittedly, couldn't. I just had too many questions, where do I put this, put I have this broken into components and what's needed in each, are there any extra steps I have to take to make it compatible with TypeScript? So I watched a YouTube video, then another, and yet another. Because none of them exactly fit my project setup and use case. But I spent the time in each, using my internal monologue to describe what each step in the video was doing. So, by the third video, I was confident-ish enough to bang away at my app. And, know what? It worked! I have this set to show if no one is logged in, and as soon as I logged in, it disappeared! So, now I'm back in more familiar territory in setting up the database.

32

6 Comments

🚨 We're hiring a head of engineering at Warmly,! Who's the best of the best you know? Offering a $5,000 referral bonus for direct intros to someone we hire. You can comment them in directly and then intro We're looking for an engineering leader who's highly technical and scaled a team and product during a period of hypergrowth, $4MM to $30MM+ in ~ 2 years or something similar Our app engineering team is based in the US/Brazil. Meet our Tech Leads Marcos Cury & Scott O'Connor. Our data engineering team is based in Israel. Meet Uri Steinfeld and Dror Ventura brought in from our acquisition of Immagnify (acquired by Warmly). And our QA team is based in Pakistan. Meet Muhammad Ali Arif and Abeer Khan). They're welcome to work out of anywhere. Though we all work US hours. And we have quarterly company off sites - most recently in Mexico City, Greece, and Austin Texas! Our system is complex but resilient. We process millions of real-time website visits/day, orchestrate tens of thousands of automated AI sales & marketing campaigns/day and sync hundreds of customer’s CRMs and email platforms. We move quickly but deliberately. Design, product, and engineering collaborate to come up with the best solutions. It's never a should we build it question, it's a "this vs that" question. Looking for 10x solutions, not just 2x. As a member of the exec team, they'd be part of all the top level decisions we make as a company. No politics here. Just efficient business decisions. We're all humble, open minded, and want every other member of the exec team to win. Know anyone that comes to mind?

91

10 Comments

Can you provide some perspective on interviewing for a Rails developer job today? I have not interviewed for a job since before Obama was in office. I am frequently asked for my advice on how to land a job. I had a friend reach out with the following message. >> Do you have any advice you can give, or perspective on what you would look for in hiring a mid level RoR dev position? We certainly hire people like my friend but with don’t currently have any positions open and I don’t think our interview matches what many people expect. I want to help them be successful. What advice would you share with this person?

7

12 Comments

Quick thoughts on the state of QA hiring as we wrap up 2024. You can still find rockstars, but it’s harder than ever. I genuinely don’t know how a startup or busy enterprise team would find the time to do this. On average, we spent 97 hours to find a candidate we’re ready to offer to. This is up from prior years. Here’s a super quick/rough breakdown of the time spent: Initial Screening: 1500 minutes (30 seconds per) for 3000 candidates. Sending Messages: 750 minutes (3 min per) for 250 candidates. Review Tech Evaluations: 960 minutes (8 min per) for 120 candidates. First Interviews: 1800 minutes (60 min per) for 30 candidates. Second Tech Evaluations: 120 minutes (15 min per) for 8 candidates. Final Interviews: 720 minutes (180 min per) for 4 candidates. Total Time Spent: 97.5 hours for a single hire. Biggest shift in 2024? The rise of AI-driven application practices. This is based on two key observations: 1. A huge spike in applications when a job is posted, with significantly lower response rates from candidates in that spike. 2. More tech evaluations being dumped into AI tools like LLMs for solutions and then submitted regardless of whether it works. What’s more troubling: many candidates can’t explain the code they “wrote.” This highlights a critical AI risk: even when correct, humans must understand the solution to catch errors when it isn’t. The good news? The right candidates see tremendous opportunity in QA as a career path. They know that embracing and mastering new technologies can create real value. Thoughts on navigating this evolving hiring landscape? Would love to hear them! #QA #Hiring #TechRecruitment #AI #CareerDevelopment

54

17 Comments

Consider software development job postings. I've been reviewing many. Hiring managers, would you be happy with (and interview) someone applying who'd be proficient in your specific skills two weeks after you hire that person? If so, please consider putting specific programming languages in the preferred qualifications and not mandatory, essential requirements. And get help - often - in ensuring your job descriptions (and classifications) are current on technical jobs. HR needs to build a habit of reviewing and renewing them more often for tech jobs, including compensation. Your organization will have its own subset environment - "How we do Python." "How we do .NET," and if that's documented and systemic, new hires will be productive even faster. Also, a closer match than expertise in a specific language is methodology - patterns - and understanding of architecture across languages. Not seeing a lot of application security listed in job duties or in qualifications. That'll change. The other thing I see that has me shaking my head is the requirement of a Bachelor's in a technical discipline AND 10 years of experience. A general Bachelor's degree will do just fine for someone over 10 years of qualifying experience (if you want to hang onto that Bachelor's requirement.) It, too, can probably migrate to the Preferred Qualifications unless the job is in management/leadership. Using me as an example, my 1994 Bachelor's Degree in Communication Management is worth about the same (or more) than if it were in Computer Science...at this point. P.S. Yes, I know - modern stack requires modern stack experience...at least most of the time. Happy to argue that even that maybe isn't the case.

24

13 Comments

Accessibility Tip of the Day 275: It's Election Day in the US, so here's a reminder that disabled individuals can face significant barriers to voting, either through inaccessible web content or inaccessible physical locations. Things like the following can help: - Allowing voting by mail - Allowing early in-person voting - Accessible websites for voter registration - Accessible websites containing candidate information - Better training for election officials on how to help disabled individuals at in-person voting locations The Election Assistance Commission has a bunch of good resources online, including a series of training videos. You can find them here: https://lnkd.in/gDcc-xFz #accessibility #a11y #accessibilityTipOfTheDay

1

What's the real cost of not involving developers early? ...Yes, involving developers early means more meeting hours. But the cost of NOT involving them? ↔ Constant back-and-forth clarifications ⏳ Rework and delays ⛓ Team disconnection 😑 Frustration ❓ Anything you'd add? Question for you Product Leaders out there: What's the costliest 'hidden' expense you've seen from leaving developers out of early product discussions? Do you agree that we should involve developers early on? What positive examples have you seen from involving developers early in the product process? Thank you so much to Eric Cussen for enriching our recent webinar. #ProductManagement #Agile #Leadership #ProductDevelopment #EngineeringCulture #ProductStrategy

15

I've seen a lot of bugs. (No, not another cicada post). Software here. Egregious, immediately noticeable bugs. The opposite - those that require 6 concurrent conditions and 6 hairs from your nextdoor neighbor and it still only triggers once a month. (Okay, 7 conditions, 6 hairs...don't split those hairs). A continuum of buggage. Those complicated ones, sans the hyperbole - those are your Zero day issues. Regression testing doesn't find them. A super wily code-reviewing look-at-it-all software QA professional (I know the best one)...might...but probably not. How do we even engineer testing all of the complicated conditions? The interrelationships at runtime? I don't see a lot of talk about "how could we have caught this?" in public for disclosed issues. Most of the fixes for Zero days (those security holes best known because they're patched with updates to software like Google Chrome browser, Apple's ioS, Microsoft Windows) are downplayed. You get "Hey, user, look at these new features you're getting, and in whispered voice, "and security updates." Not familiar with the term? Zero day means a security issue without a patch. When the patch arrives, there's a remedy for the problem. Users often don't APPLY the remedy until much later...its own problem...prolonging the risk of the Zero day issue. Back to my kinda silly example. That's a wicked hard problem to test for. A bunch of concurrent situations that then trigger the problem. But, when the problem's a known issue, it's not hard to re-trigger. And therefore exploit. So what do we do? Other than fixing/patching, and communicating? What else is there to add to this conversation? Sunday thoughts. Sunday thoughts.

13

7 Comments

Right now, the market sucks. One reason it sucks is that applicant pools are too large. For any opening, hiring managers get hundreds of applications immediately. How does your application stand out from the hundreds or thousands of other applicants? In this episode of our Essentials of Finding Your Next UX Job video series, I discuss what steps you can take to make your application stand out to hiring managers immediately. I uncover how to make it apparent that you’re qualified and a great fit for the position they're hiring for. https://lnkd.in/e4Abvssu

10

7 Comments

Right now, the market sucks. One reason it sucks is that applicant pools are too large. For any opening, hiring managers get hundreds of applications immediately. How does your application stand out from the hundreds or thousands of other applicants? In this episode of our Essentials of Finding Your Next UX Job video series, I discuss what steps you can take to make your application stand out to hiring managers immediately. I uncover how to make it apparent that you’re qualified and a great fit for the position they're hiring for. https://cstu.io/281ab7

9

2 Comments

Right now, the market sucks. One reason it sucks is that applicant pools are too large. For any opening, hiring managers get hundreds of applications immediately. How does your application stand out from the hundreds or thousands of other applicants? In this episode of our Essentials of Finding Your Next UX Job video series, I discuss what steps you can take to make your application stand out to hiring managers immediately. I uncover how to make it apparent that you’re qualified and a great fit for the position they're hiring for. https://cstu.io/c1d235

11

Right now, the market sucks. One reason it sucks is that applicant pools are too large. For any opening, hiring managers get hundreds of applications immediately. How does your application stand out from the hundreds or thousands of other applicants? In this episode of our Essentials of Finding Your Next UX Job video series, I discuss what steps you can take to make your application stand out to hiring managers immediately. I uncover how to make it apparent that you’re qualified and a great fit for the position they're hiring for. https://cstu.io/d411bc

5

Right now, the market sucks. One reason it sucks is that applicant pools are too large. For any opening, hiring managers get hundreds of applications immediately. How does your application stand out from the hundreds or thousands of other applicants? In this episode of our Essentials of Finding Your Next UX Job video series, I discuss what steps you can take to make your application stand out to hiring managers immediately. I uncover how to make it apparent that you’re qualified and a great fit for the position they're hiring for. Check out the website here: https://cstu.io/f2e2c9

1

Hey LinkedIn network, I need your help! Does anyone know of any open roles for Solution Engineering or manager of solutions roles? I have a few people that are looking for their next play in this space. Either comment on this post or send me a message. Appreciate any help with this!

15

A junior software developer might evaluate a career path. Common options available after some seasoning are senior software developer, software architect, and project manager. Software development managers. Delivery managers. Hop on over to QA if you like to break software. This slight field shifts requires you to develop some maniacal laughter strains. Might shift into DBA, or database administrator, work, too. Some of the most valuable career exploration is determining what you like and don't like. Martin Fowler's book Patterns of Enterprise Application Architecture (not pictured), while well organized and brilliant, taught me I did NOT want to be a software architect. And that was important to learn early. The book pictured here is the Fowler's I more easily identify with - modern English usage in writing. My copy of Martin Fowler's book is currently at the Missouri Cybersecurity Center of Excellence SOC. I figured this swapping out the books was almost as amusing as AI black cats. I'll be writing a whole lot more about my work at MCCoE in future posts...but for today... Like software development, cybersecurity offers a great many career options. Early learning should provide context and insight into where to focus to learn the foundational basics. Why? So that the learner is well rounded and also able to later specialize in the right area of interest while serving well in the current role. Self-taught people need mentors to help identify the path, and this field is one of the best in giving back to the community of the aspiring next generation. I'm frequently amazed and pleased to play a part. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I learned in the first couple of years that my tech career needed to focus on people and their needs. Software is, after all, built for people. It should make their work easier and their lives better. Please, someone else make it run faster and leaner, and I'll verify flows well and the data that powers it is accurate. Fowler's Modern English Usage only mentions cybernetics, not cybersecurity. "... a by-product of the word is the use of the first element -cyber in a wide range of computer terms such as cyberphobia, cyberpunk, and cyberspace, or virtual reality..." #cybersecurity #career

14

4 Comments