Michela Federico

Bounties Available 🤠 If you are a Scala, Kotlin or Java developer and are looking to help out the community whilst adding some extra cash in your pocket, then you probably want to follow Haoyi Li's Reddit thread 🧵 This thread is growing, here are how the total bounties look from the past few months; May: $2,500 paid 💰 July: $1,000 paid 💰 September: $10,000+ available! 🤑 If you want to see if there is anything you can help with, then take a look here:

24

1 Comment

Adding Custom Color Themes to Tailwind CSS https://lnkd.in/er4w9Q_k

6

Just throwing this out here and see if it sticks. I'm toying with the idea of creating a new course focusing on API development and testing, with the target audience being at the minimum both developers and testers, both potentially also folks in other roles. In this course, we'd incrementally design, build and test a small API, introducing different types of tests (unit, integration), areas of interest (logic, contract, security), and exploratory testing techniques and automation tools along the way. The learning objectives are multidimensional here: * Testers learn a bit more about API development (and API testing) * Developers learn a bit more about API testing (and API development) * Everyone learns a bit more about how to work together on doing this and what a solid, incremental approach to API testing would look like I'm pretty confident I could offer this in Java (Spring), C# (ASP .NET Core), Python (Flask / FastAPI) and JS (Express), and maybe even other frameworks, too. I'm just wondering if there would be demand for a course like this. What do you think? Am I missing anything?

52

14 Comments

You probably know this, but you probably still don't do it enough 🤓 Keep your components small!🚀 This is one of the slides of my new #Angular Architectural patterns course that is filled with best-practices I've acquired from being involved in over 150 Angular projects. The course isn't ready yet, so stay tuned or subscribe on the simplified courses website.

13

1 Comment

TypeScript 5.5 – It's a Banger! It's been slightly more than two weeks since the release of TypeScript 5.5, and if you haven't explored the latest updates yet (just like me 😊), I highly recommend checking out this insightful video by Matt Pocock [https://lnkd.in/gdVeWBni] The new features include Set methods, regex syntax checking, inferred type predicates, and many more exciting additions. My favorite update is the new tsconfig template variable configDir, which enhances support for monorepos. Setting up those three levels of tsconfig used to be quite tricky, and this update makes it significantly easier. Check out the full release notes here (https://lnkd.in/gNKy-5F7). What's your favorite update? #TypeScript #TypeScript5_5 #JavaScript #WebDevelopment #Programming #Coding #SoftwareDevelopment #TechUpdates #DeveloperCommunity #Angular

23

Check out the new architect resources that are coming in May 2024 in our latest blog post. Learn more in our latest post by Shoby Abdi.

1

Don’t write ‘as many tests as you can’. Write as few of them as you can get away with, and then make those tests really good. Ideally, have a suite that runs in seconds, or a few minutes tops, and one that, when passing, gives you enough confidence to say ‘this build is ready for deeper testing’. Weniger aber besser. Less but better.

254

30 Comments

Devs, do code challenges and tech tests give you the interview ick? 🤮 Taking to lots of young devs at the moment and they keep telling me that they’re finding the tests and challenges a real turn off! It sounds like companies are just plonking in challenges and tests that they haven’t thought through, or actually done themselves! 😏 Irrelevant, wrong tech, laborious, poorly designed and executed.❌ With horrible cold automation that just flat out rejects you! 😡 Hey Devs, I’m sure employers would love to hear about your experiences? I hear LeetCode isn’t great. Any others you’re liking / not liking? Please, we’d love to hear all about it…..Come on, it’s feedback time….for you! 👀 And don’t hold back 😳 #interview #theick #candidateexperience

6

3 Comments

💥 JAVASCRIPT TRENDS & FRAMEWORK UPDATES 💥 JavaScript continues to evolve in 2024 with exciting trends in Frontend & Backend frameworks and tools. TypeScript adoption is soaring, enhancing code quality and developer productivity. Frameworks like React 18 and Vue.js are being joined by Svelte for more efficient, lightweight applications. Server-side rendering with Next.js and Nuxt.js is gaining traction for faster, SEO-friendly websites. Check out the slides below for framework updates 👇 👇 👇 #javascript #tools #frameworks

41

3 Comments

🚀 Are you leveraging your mistakes for growth? 💪 In the world of software engineering, mistakes are not just inevitable; they're a goldmine 🏆 for personal and team development. It’s through these errors we truly learn the resilience and adaptability required to lead 💼 in tech. Reflecting on and sharing these lessons not only humanises us but fosters a culture of continuous improvement and innovation.🔄 Embrace your errors, analyse them, and share the learnings with your team. This approach doesn't just solve problems—it turns them into stepping stones 👣 towards success. 🚀 #GrowthMindset #SoftwareEngineering #TeamDevelopment #Growth #Career

1

1 Comment

I'm glad Jack 🤔 Herrington touched on the value and use cases for mono-repos in this last #NextJS course called Project Setup and Infrastructure. Much more was covered to demonstrate how to set up your applications for long-term success. #Storybook, #Testing, #CI/CD, #Linting

7

Check out our latest blog post on Playwright showing you some cool tips and tricks on how to best use --only-changed such as in pre-commit and pre-push hooks. :) https://lnkd.in/dMJ-74Z3

30

UPDATE: I figured it out and learned an important lesson - when testing React components make sure to name your file with a .jsx extension, not .js. 🤦‍♀️ 🚧 Calling any and all testing experts! I'm having issues with happy-dom... I think that's the issue anyway. I was really excited about the DOM testing section of the Frontend Masters course, but really just went over the lessons on configuration and some basics. I thought I'd be able get started, but I keep getting this unhelpful error: Expression expected. I installed @testing-library/react, @testing-library/jest-dom, vitest and happy-dom. I think I configured it in vitest.config.js: import { defineConfig } from "vite"; import react from "@vitejs/plugin-react"; export default defineConfig({   plugins: [react()],   test: {     include: ["**/*.test.js"],     environment: "happy-dom",     globals: true,     setupFiles: ["@testing-library/jest-dom/vitest"],   }, }); But I can't get any tests to run on my component. I'd appreciate any suggestions you very fine & smart folks have! As a bribe, I can offer audio recordings of my mini pig snoring in her sleep. 😁

23

8 Comments

I gave a talk at the most recent London Ruby User Group (#LRUG) on how experienced programmers solve problems, and what that means about how we think and communicate as human beings: https://lnkd.in/eBzTM53t I am really proud of this talk and care deeply about this subject; I'd love if you could give it a watch! (slides available here: https://lnkd.in/eXX89qXe)

38

Ownership between engineering teams is extremely hard topic. Specifically when teams are owning part of the app / framework / API. And from my experience it always goes through some weird cycle: 1. Component created, everyone starting contributing to it. Obviously, there is no guidelines, generic principles, or even code style. When everyone owns something - that means that no one responsible. 2. Eventually component become critical for business, errors in this component becomes more expensive, time to support it - increasing. Business decided that some team need to own this component. 3. Owning team will start paying tech debt for all these years of mindless committs, refactor something, rewrites. 4. Since guidelines are still not prepared, and component is still kind of messy - owning team does not allow anyone to commit there anymore, or asking tons of changes to merge request. To the point that no one wants to work with that team, or touch that component. Instead of this teams starting creating feature requests. 5. Business can’t be stopped, so owning team starts satisfying those feature requests with paying tech debt in parallel. More teams coming up with feature requests, and owning team starts drawning under never ending requests. They coming up with prioritization frameworks, which always makes someone unhappy because of lower priority of their requests. 6. Finally when team is tired, burned out, and their backlog is way larger than they can consume - someone come up with contribution model - list of guidlines, instructions and requirement on how other team can contribute to the component. Congratulations - now you have a platform team! What will be more optimal way? Create contribution model / guideline generic for the whole company, and apply it every time when more than one team using same component. Save your people :)

57

5 Comments

🚀 Exciting Times Ahead for Software Testing! 🚀 I've been diving into the capabilities of the new Claude 3.5 model, and it's clear we're at the forefront of a shift in how we approach software testing. With its ability to simulate user interactions and behave like an actual user, we can now: Run comprehensive end-to-end tests, covering user journeys from start to finish. Improve usability testing, gaining insights into UI/UX and accessibility. Automate interactive and functional tests, ensuring all user inputs and workflows are seamless. Perform exploratory testing in ways that mimic real user behavior, catching edge cases we might not think of. Conduct load and stress tests that simulate thousands of users, helping identify performance bottlenecks before they hit production. Ensure cross-platform consistency, making sure the experience is smooth across all devices and environments. This level of automation and realism is not just a game-changer—it redefines what we consider possible in software quality assurance. I'm genuinely excited to see how these capabilities will evolve and transform the way we think about testing our software. What do you think the biggest benefit of AI-driven user simulation in testing will be for our industry? Let me know your thoughts below! #automatedtesting #aitesting #testing #softwaredevelopment

9

4 Comments