We're #hiring a new Regression Test and Development Engineer in Austin, Texas. Apply today or share this post with your network.
Proiasys Inc’s Post
More Relevant Posts
-
Senior Engineering Manager @Zee | Mentor | YouTuber | Career Coach | Educator | Ex - Baazi Games | HealthKart | Paytm | ShopClues
'Type -3 ' Engineers: "There's a bug. Someone should fix it". 'Type -2' Engineers: "There's a bug. Do you want me to work on fixing it?" 'Type -1' Engineers: "There was a bug. I fixed it and made changes so this bug can't happen again. I've also added alerting so in case a similar bug happens we'll know faster next time. #engineers #technology #bugs
To view or add a comment, sign in
-
Founder/CEO at AEDVICES - !!! HIRING !!! Design & Verification / Design House / Trainings !!! HIRING !!!
Being a verification engineer is making real life difficult. As a verification engineer, when the specification says “the input data can go up to N”, we have to verify that you can drive N and you expect that the result is fine. So, when a well-known administration tells you that you have 14 days to sign the contract, and explicitly says that you have up to 22/01/2024 to sign, you may expect that you can sign on 22/01/2024. I know that some of you will advise me not to wait for the last minute. The last minute is actually later tonight, so I still have time and there were other priorities to deal with before. Now, that day I expect to be able to sign that contract. This is not couting on the developer who used the strict comparison < instead of less or equal <= So 14 days actually means 13 and up to 22/01/2024 means 22/01/2024 early in the morning at 00:00. Hopefull there are people behind the machine (for how long ?), but this is so much time lost just getting the case back on track, explaining the issue to non technical people, because there is a developer who didn’t test the boundaries…. A few messages: Developers, think twice when using < and not <= (or vice versa). Developers, I hate you today, you ruined my day. Developers, I love you, there is so much verification work to do in so many areas ! Everyone, don't play Verification Engineer game in your day to day life ! #verification #cornercase #test #developpers
To view or add a comment, sign in
-
-
Software Architect | Coaching & Mentoring | Consultant & Advisor | Innovation Catalyst | Problem Solver
N Engineers: “There is no bug! We cannot reproduce it.” Z Engineers: “We know about this bug! We need to prioritize it in the next sprints!” Way better classification than Senior/Mid/Junior. Probably the best way to measure developer performance. All developers are writing code with bugs, no matter the experience, but the attitude around how to fix a bug or measures taken to prevent similar ones is the metric to track in analyzing performance.
'C' Engineers: "There's a bug. Someone should fix it" 'B' Engineers: "There's a bug. Do you want me to work on fixing it?" 'A' Engineers: "There was a bug. I fixed it and made changes so this bug can't happen again. I've also added alerting so in case a similar bug happens we'll know faster next time.
To view or add a comment, sign in
-
Software Engineer III ► Keen interest in: Front-end Development | Design | Automation ► Guaranteeing continuous improvement to SAAS products..
This post is phrased in a way that makes the A type of engineer seem optimal. I'd argue that in many fast paced time sensitive companies the B engineer is the one's you want on your team. Naturally when presented with a problem Engineer's will want to solve it. But we have to always ask is this the most important thing we could be working on at the moment? "Great job C engineer, you took the initiative and fixed the bug and now everyone will know not to make that mistake again." This is what we expect a response to be for doing that but what if the response is this instead: "Well Thank you C engineer for taking the time to fix that bug. I hope you didn't spend too much time on that issue tho. It does not impact that many customers and the tasks we originally agreed upon that you said you would work on were aligned with a marketing campaign that will go live this afternoon. So, how is that coming?" As I come across bugs unrelated to task I'm working on, I alert the team with my findings and then continue my work. Usually I get word pretty quickly from the Product Owner if that bug is urgent or not. If it is, we see what can we put on lower priority to fit the bug in and if not we put it on the backlog to pick up when we can. (This post is in no way trying to take anything away from the original post Ryan makes here. It is simply a thought I had after reading it.)
'C' Engineers: "There's a bug. Someone should fix it" 'B' Engineers: "There's a bug. Do you want me to work on fixing it?" 'A' Engineers: "There was a bug. I fixed it and made changes so this bug can't happen again. I've also added alerting so in case a similar bug happens we'll know faster next time.
To view or add a comment, sign in
-
What are the most important things systems engineers don’t understand about software engineering? What are the most important things software engineers don’t understand about system engineering?
To view or add a comment, sign in
-
Do you feel like integration is the word that describes most of what we do as software engineers? Integrate ideas with technology with people.
To view or add a comment, sign in
-
Handling ambiguity well is a key component to advancing as a software engineer. How do you quantify "ambiguity" without being hand-wavy? Here's a framework for how to think about ambiguity at each engineering level (see attached screenshot): 1. Junior (IC3) - No ambiguity. We know exactly what we need to do, project just needs to be completed. 2. Mid-level (IC4) - Feature-level ambiguity. We know the solution but don't know the details of how to implement it yet. 3. Senior (IC5) - Roadmap-level ambiguity. We know what problem to solve and why, but we don't know what to do to solve it yet. 4. Staff (IC6) - Strategy-level ambiguity. We don't even know what problems we should tackle. IC6s create scope. If you have another way of thinking about engineering ambiguity I'd love to hear it. How do you quantify ambiguity?
To view or add a comment, sign in
-
-
Post Si Validation/Debug engineer | Power Management | GPU | Chipset Debug | Silicon Platform Debugging
Hello everyone, I hope this message finds you well. I am currently exploring new career opportunities within the semiconductor industry. As I navigate this exciting phase of my career, I would be grateful for any support or guidance you can offer. Thank you in advance for any connections, advice or opportunities you can offer. #PostSiliconValidation, #QA, #ManualTesting, #Debug #PowerManagementTesting, #GraphicsDriverValidation, #Power, #FeatureTesting, #FunctionalTesting.
To view or add a comment, sign in
-
Efficient exception handling is a necessity for alerting systems.
'C' Engineers: "There's a bug. Someone should fix it" 'B' Engineers: "There's a bug. Do you want me to fix it?" 'A' Engineers: "There was a bug. I fixed it so this bug can't happen again. I've also added alerting so if something similar happens we'll know faster next time."
To view or add a comment, sign in
More from this author
-
Unlock the Power of Seamless Data Exchange with EDI Consultants - Find Your Strategy and Implementation Experts Today!!
Proiasys Inc 1y -
Unethical Practice of Renegotiating Vendors: Ensuring a Smooth Onboarding Process
Proiasys Inc 1y -
The Crucial Link: Mental Health and the Success of Business Owners
Proiasys Inc 1y