Framework’s Post

A little under two years ago, I started working for Framework with absolutely no idea how much I would learn, grow, and explore at this company. For those of you who haven't heard of us, Framework makes consumer electronics that are repairable, upgradeable, and customizable. Framework's roots began in the incredible communities of right-to-repair enthusiasts, engineers, Linux users, and PC builders, but the mission that Framework champions is for everyone. The consumer electronics industry depends on you purchasing a product that lasts a few years before it becomes obsolete and you buy another one. New generations keep coming out. E-waste keeps building up. Framework dares to do it differently, designing products that are meant to last. In four years we've launched five laptops and we're just getting started. Follow us on social, check out frame.work, or make the ultimate commitment and help us change the consumer electronics industry by applying to one of our open roles at https://lnkd.in/g6fpTndS

🚀 Exploring the World of Software Quality! 🌐 Hey All👋 Ever wondered about the different roles ensuring top-notch software quality? ➡️ 🚩Quality Assurance Engineer Responsibilities in Software Development:➡️ 🎯 Accountable for product quality using both manual and automated testing methods. 🎯 Ensures software development lifecycle processes adhere to quality assurance standards. 🚩Quality Engineer (QE) Responsibilities in Software Development:➡️ 🎯 Applies engineering practices to enhance quality in software development. 🎯 Ability to craft a quality plan, edit code, and comprehend the project’s overall business vision. 🚩Software Development Engineer in Test (SDET):➡️ 🎯 Focuses on test automation, framework development, and a deep understanding of systems. 🎯 Advises development, management, and design teams on technical implementation and user scenarios. #QualityAssurance #SoftwareEngineering #SDET #QualityEngineer #LinkedInNetworking 

Junior Engineer: "How should I build it?" (implementation details) Mid-level Engineer: "What should I build?" (solution-level direction) Senior Engineer: "Why should we build it?" (problem-level direction)

Your technical skills are the LCM, the lowest common metric. No one expects a software engineer not to be able to code. There are always fine engineers out there. When it comes to technology teams and indeed every team, the distinguishing factor is the ability to work as a team. Individual members might be brilliant but if that handshake between engineers does not happen (Data, Product, Design, Core Engineering and QA), nothing worthy of note shows up. The finest attribute of any engineer I have seen is their ability to work harmoniously together with especially their direct team members. Then, there's the willingness to go that extra mile. You will be just fine covering your regular grounds. But that's it. You will end up regular. And that's great for the most part. However, if you are looking to stand out, that team work, that little extra is what gives you that likelihood to stand out. #AskPyFesh

Software engineers could benefit from more of an engineering mindset. Other types of engineers out there, working on stuff in the "physical world", are much more conscious of the impact of their work. I would argue that in general, as software engineers, we have it the easiest out of all engineers. 𝗪𝗲'𝗿𝗲 𝗴𝗼𝗼𝗱 𝗮𝘁 Problem solving Systems thinking User centered design 𝗕𝘂𝘁 𝗼𝘁𝗵𝗲𝗿 𝘁𝘆𝗽𝗲𝘀 𝗼𝗳 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗼𝘂𝘁𝗰𝗹𝗮𝘀𝘀 𝘂𝘀 𝗶𝗻 Planning Precision Robustness Redundancy Safety and security Environmental awareness In software we don't have to work with concrete, steel, scarce minerals, synthetic chemicals, etc. Sure we also have clean code, testing, QA, and our principles. But we have the huge luxury of iteration, of moving fast and breaking things! And it allows us to rapidly innovate, which is awesome 🤗 However, I marvel at other types of engineers out there. Who have to get it right the first time. And I think we should aspire to be more like them. #programming #softwareengineering #engineering

Junior Engineer: "How should I build it?" (implementation details) Mid-level Engineer: "What should I build?" (solution-level direction) Senior Engineer: "Why should we build it?" (problem-level direction)

Engineer 1: "I am going to write comments, create documentation explaining what's going on, and double check my variable/function/class names so everything is intuitive and makes sense." Engineer 2: "I'm going to write a bunch of code that tests all of your code. We don't need docs because my test functions are the documentation. If a bug/crash gets into prod its also not my fault either. I'm just pointing out everything wrong, creating tickets, and reporting to management." Engineer 3: "I am going to do what Engineer 2 does before I do what Engineer 1 does."

What makes a Senior Engineer "senior"? It’s all in the details. Often, people think seniority is just about years of experience or handling large-scale systems, while these can be part of the mix, a key ingredient in the making of a senior is - attention to detail and the careful crafting of code - not necessarily the complexity of code. For example, consider a simple function like this one I wrote to format a number: Here, I made sure to handle potential edge cases: If the input isn't a valid number, it logs an error and returns a safe fallback. For numbers less than 10, it formats them with a leading zero, ensuring consistent output. It’s the kind of "thoughtful programming" that prevents headaches down the line. It's not just about making the function work; it's about making sure it handles as many edge cases as possible, providing reliable, maintainable, and predictable behavior. This, I believe, is one of the things that separates junior and senior engineers: the constant mindset of anticipating and avoiding issues before they arise. #SoftwareEngineering #CodeQuality #EngineeringMindset #AttentionToDetail

🚩The most important characteristics for a software quality engineer include: 1. **Attention to Detail**: Ability to identify even minor issues in software functionality and performance. 2. **Analytical Skills**: Strong problem-solving skills to analyze complex systems and understand user requirements. 3. **Technical Proficiency**: Familiarity with programming languages, testing tools, and methodologies. 4. **Communication Skills**: Ability to clearly articulate issues and collaborate with developers and stakeholders. 5. **Critical Thinking**: Capacity to assess the quality of software objectively and suggest improvements. 6. **Adaptability**: Willingness to learn new technologies and adapt to changing project requirements. 7. **Time Management**: Efficiently prioritizing tasks to meet deadlines while maintaining quality standards. These characteristics help ensure that a quality engineer can effectively contribute to the software development process and deliver high-quality products. #SoftwareQuality #QualityAssurance #Devops #QualityControl #QualityAssuranceJobs

Junior Engineer "How can I make this code work?" Mid Level Engineer "How can I make this code work well?" Senior Engineer "How can I make this code work well for the next engineer who touches it?" The better you get at coding, the more awareness you have for the people using your code. #softwareengineering