Ed Frederici

Are your software teams efficient? Below are some of the critical questions I ask myself in order to try to build a high caliber software organization. I also think that Quality -> Consistency -> Acceleration -> Innovation all have to be addressed in that order to be successful. Thought I would share with you all, let me know what you think!

28

3 Comments

I envision a better alternative to Backstage: reusing an existing script and adding an intuitive interface. That's essentially what most people expect from a self-service portal for their software engineers — nothing more. #internaldeveloperportal #devex #developerexperience

5

Super excited to be speaking at #DrupalCon Portland next week! My session, "A Migration is a Terrible Thing to Waste: A Roadmap For Your Next Big Content Migration," will show you how to turn a herculean effort into a strategic win. Content migrations are stressful, but they're also a chance to improve your content, tools, and workflows for the future. Join me to learn: - Planning tools for a smooth transition - Strategies to avoid errors, downtime, and SEO dips - Techniques to enhance your content during migration - Uncovering hidden opportunities you might miss Your content and data are as important as your tech stack. Let's make your next migration a success story! 🚀 #DrupalCon #ContentMigration #Drupal

66

8 Comments

Interview tip #4, y'all: let's talk about the coding assessment! First off, let's get the elephant out of the room: some jobs use automated technical screening platforms that assess your code against a set of tests/metrics/etc. These are bad and dumb and do those teams an incredible disservice. They're rarer than you think, but still much more common than they ought to be. If you've gotta do one, just do your best and hope they have a better screening process beyond it. I consider that practice a 🚩. 🤝 A healthy coding test relies on collaboration, just like your work on the job. You might be asked to work on a problem or project independently and then discuss it during a live interview later, or you might be asked to write some code live for an interviewer or panel. Here's the most important thing to remember: 𝐢𝐭'𝐬 𝐲𝐨𝐮𝐫 𝐓𝐇𝐎𝐔𝐆𝐇𝐓𝐒 𝐭𝐡𝐚𝐭 𝐜𝐨𝐮𝐧𝐭! Yes, you are being assessed on technical competency, but just brute-forcing through a solution in silence can be just as harmful as if you couldn't write code in the first place. Your interviewers want to understand how you're making your decisions and what trade-offs you're aware of. This can be scary in the moment. Here are some frameworks to check out that can help you feel confident: - "OICE" is an acronym for "Outputs, Inputs, Constraints, and Edge Cases". It's a simple way to verify your assumptions about a problem, establish a path forward, and demonstrate that you're taking a thoughtful approach before you write the first bit of syntax. You can read more on Medium: https://lnkd.in/eTRZTQc7 - "PREP" goes a little farther - "Parameters, Returns, Examples, and Pseudocode" takes you beyond just establishing what's needed and helps you practice writing out simplified algorithmic approaches. PREP is especially good for problems that feel really big. Even if you can't write a full code solution due to time constraints or technical challenges, you've already shown what you were working towards. Again, Medium has some more context: https://lnkd.in/eRRXyvZT These are great tools, but they don't mean anything if you can't deploy them on demand. To use them well you have to practice! Load up CodeWars and phone a friend - ask them to pick any problem at a difficulty level you know you can crush, and practice writing out just the framework portion of your approach. 💡 This is just as important as practicing your syntax! Being able to justify and explain the code you write is what differentiates you from every LLM on the block. ChatGPT can solve most problems faster than you, but it can't pick the most appropriate solution for a specific context without a lot of help and prompting. You, dear engineer, totally can! 💪 Flex that brain and learn to love the meta of coding, and these scary challenges become opportunities to show off your communication skills.

18

2 Comments

I read this amazing blog post over the weekend from Zack Urlocker & thought there were some interesting parallels to empowering decision making on QA teams. My takeaway: Pushing decisions down to the people closest to the work is one of the most powerful ways to increase ownership, accountability, and speed of execution. As QA professionals, we are intimately familiar with the products and systems we test. We understand the requirements, user flows, edge cases, and potential risks better than anyone. By empowering QA teams to make more decisions around testing strategies, prioritization, risk assessment, and quality gates, organizations can unlock several key benefits: Increased Ownership and Accountability - when given autonomy to make decisions, QA teams take greater ownership over the quality of the products they deliver. This drives a sense of accountability and responsibility to ensure thorough testing and high standards. Empowered teams are motivated to proactively identify and mitigate issues. Leveraging Expertise - QA professionals have deep domain knowledge from their hands-on experience with the product. Empowering them to make decisions allows this expertise to be fully leveraged in determining effective testing approaches tailored to the specific product needs. Faster Execution - with the ability to make decisions autonomously, QA teams can streamline testing processes, adapt quickly to changes, and provide timely feedback. This accelerates identification and resolution of issues, enabling faster delivery of high-quality products. Fostering Innovation - when given the freedom to make decisions, QA teams are empowered to get creative and innovative with their testing methodologies. They can experiment with new tools and techniques to continuously improve quality processes. Of course, empowering QA teams requires a foundation of trust from leadership and an investment in training to build decision-making capabilities. But the potential benefits of increased quality, efficiency, and innovation make it well worth the effort. Pushing decisions down cultivates an environment of trust and accountability that unlocks incredible potential. Let's embrace this mindset and empower our QA teams to make more decisions - the quality of our products will be better for it. #QualityAssurance #QATeams #EmployeeEmpowerment #AutonomyAtWork #DecisionMaking

14

2 Comments

Mike and I started a company six years ago to scratch our own itch. At the time, we didn’t have a tool that complemented our agile practices. This is why we created Team O'clock: To help teams of any size get the most out of their agile meetings. With Team O’clock, you can: - Assess the effectiveness of your agile practices with in-depth metrics - Build and reward positive agile practices with Agility Cards - Speed up your workflow with the help of AI All without jumping from app to app. Interested? Learn more about Team O’clock. 👉 https://bit.ly/432amEU

13

Commit Notifications should not be giant walls of text. Commit Notifications should not be sent to Slack nor Teams. Commit Notifications should be tailored to the individual user. Commit Notifications should not skip material content just because you missed the scrolling wall of channel messages. Commit Notifications should should not drown you in self notifications.

1

1 Comment

As a dedicated fan of PoolSuite FM, I've taken matters into my own hands. With no Android version available, I'm leveraging NativeScript to create my own. Follow my journey through this tutorial series and witness the progress firsthand! #PoolSuiteFM #AppDevelopment #NativeScript #Vuejs #AndroidDevelopment #WeekendProject

1

RSVP: July 19: 12pm EST: Modern #softwareengineering (Building Better Software Faster), with Dave Farley https://lnkd.in/eE9iFRry What really works to help us build better software faster? What are the fundamentals of our profession, that if we get them right, and apply them whatever our goal and whatever our technology, will increase our chances of success. Some of these ideas have been hiding in plain sight, and if we just take them and build our practice and process on them, we do get better results. So what are they, what does that take, and what are the hallmarks of great software development? In this talk Dave Farley explores these ideas, and with examples from software and other industries illustrates each of 10 ideas that when combined can be used to form the basis of a modern, agile, engineering approach to software development. Dave also answers the question “what does ‘quality’ in software really mean?”. #softwaredevelopment #morewithless #organizationaldesign Bastiaan van Hamersveld Frans Meuwissen RSVP: https://lnkd.in/eE9iFRry

16

Media coverage of technical interviews recently has highlighted that too many companies are asking too much of candidates -- while not even really honing in on the right things. Talk about a miss. Does make me wonder, though: are you clear on the full breadth of the role of #developer? It's more than whipping out some #code. Check out my video and drop a comment. #recruiters #technicalhiring #siliconvalley #techjobs #hr #interviewing

107

7 Comments

If you are an LSP using a “high touch, high maintenance” Automation platform and struggling with: - NO ROI after throwing thousands of dollars at it - Had to hire extra maintenance resources just to manage the fundamental execution of that platform - Have to contact your vendor for minor changes that take forever to get executed - Got promises this would be your way into becoming a digital “tech-enabled company that happens to move freight.” If what you need is RESULTS - more quotes, more loads - and less worrying about how you will get the ROI of an investment, we should talk. Your shippers are already choosing brokers that can respond to their quotes faster and more automatedly. Why wait? Tabi Connect can quickly get you up and running with proven ROI within days. The evidence is in the numbers and all the brokerages using our tool and winning freight. #automation #roi #logistics #lsp #3pl #freight #quotes #api #rpa #freightquote #freightech

11

Yes, requirements are important. In the tech/software world, we've come to this very strange place in which "requirements" has become an offensive word -- "what, you want me to define the project in advance? Get away from me, you waterfall devil." Even more bizarre, we've come up with all kinds of innovative names for the same thing so as to appear that we don't see the naked emperor. I am proud to say that I've driven more successful projects than I can hope to remember, and each started with -- yes, a requirements document. That is why I was thrilled to see research from the Register indicating "that projects with clear requirements documented before development started were 97 percent more likely to succeed." (1) I promise you, no project has ever failed due to an effort to understand and document the problem first, but plenty of projects have failed by not doing so. Cited: (1)

23

4 Comments

Here's a demo of my app, q.buzz

2

Is script maintenance taking up too much of your team’s time? It's a common challenge that mabl addresses with its new mobile app testing solution. 🙌 By eliminating the need for extensive coding and ongoing script updates, mabl allows your team to concentrate on innovation and user satisfaction. The low-code platform is easy enough for anyone to use yet powerful enough for complex test scenarios, making it ideal for teams aiming to accelerate their development cycles and improve app quality. Check it out now! 👇👇👇 https://lnkd.in/e524xG4k #mobileapps #mobileapptesting #mobileapptestingtools #mabl #newmobileapptesting #mobileapps #SDET #QA #developers #mobilesoftwareteams #atomationtesting #testautomation #ai #aiintesting #testcreation #testmaintenance #devicemanagemnt #testguild

5

"Our documentation is great!" said no one ever. It is always interesting to talk to folks about this problem. It'ss a problem that can be hard to grasp, measure, and even harder to solve. That is; unless you think about it in a different way. A little bit of simplification, structure, and even some AI might do the trick. I also found a new AI tool, Unblocked, while at LambdaConf this week. I am excited to start experimenting with Unblocked and think it could be a game changer when it comes to managing documents across an organization. Check out my latest article where I talk about #knowledgemanagment. Dennis Pilarinos Daniel Horton

28

1 Comment