Rui Chen

In this Inside #Java Newscast you'll get a look at the goals and history of Project Leyden, and how to evaluate Project Leyden in your projects. https://lnkd.in/edDYwDMF

1

State management is a challenging software engineering topic. State creates dependencies, and dependencies create complexity. Therefore we need to understand how to manage state. I recently heard someone say that we should aim to remove all raw for loops from our C++ codebases and replace them with std algorithms. At first I didn’t grasp his point, but I soon began to realize that he was trying to explain that raw for loops expose state. We don’t want to expose state, instead we want to encapsulate and manage state. Managing state was the topic for my talk at the Audio Developer Conference ‘23. In this talk, I share my thoughts about it in the context of JUCE (a C++ audio software framework) applications. In audio software, we have to deal with different forms of state including global settings, presets, UI state, and application state. State must be stored and restored and must be synchronised throughout the app across different threads (at least the audio and main thread). State sometimes needs to be synchronised with other software, such as a DAW (Digital Audio Workstation). There is a lot of debate about how to solve all these problems, and I’ve seen a lot of people do this in different, some good and some bad, ways. How you do it matters. It all starts by knowing the JUCE framework and understanding the fundamental JUCE objects, including the AudioProcessorValueTreeState, ApplicationProperties, Value and Vars. Knowing these objects will help you to build up a state system that suits your application. You can watch my talk now on YouTube! Go ahead, watch it, and feel free to send me a message with any question or comments afterwards. #softwaredevelopment #juce #audio #c #plugins #statemanagement

20

Github Copilot: Developers can't kick back and relax. So where is Copilot adding value? 🤔 Marcel Chabot - Development Manager at The TM Group, Inc. is explaining to a layman like me how developers get to focus on the important tasks and let Copilot take over the mundane activities. Overall, the developer leveraging Copilot will get more done, with improved quality and likely more documentation as well. Sounds like a dream. Would love to hear from others what their experience is. Has Copilot significantly improved your output? See the link in the comments for the full 30min interview. Dynamics Compass #Copilot #msdynamics #github #githubcopilot

1

1 commentaar

🚀 Exciting News for Developers! Join us on Friday, November 15th for an in-depth session on the upcoming new major version of the Fluent UI Blazor library. This release brings groundbreaking Web Components and major architectural innovations to take your web development to the next level. With Vincent Baaij https://www.dotnetconf.net 🔍 What to Expect: Overview of New Features: Explore the latest enhancements, including cutting-edge Web Components. Architectural Changes: Understand the performance, scalability, and maintainability improvements in the new architecture. Migration Guide: Yes, there will be breaking changes! But we’ll guide you with practical tips and best practices to smoothly transition your projects. Hands-On Demos: Watch the new features in action with live coding demonstrations. 📅 Don’t miss out! Mark your calendar and get ready for this transformative session. #Blazor #FluentUI #WebDevelopment #WebComponents #Architecture #Migration #LiveCoding #TechTalk #WebInnovation

38

2 commentaren

My talk at #FrontendNation is available in full length on youtube. Let me know what you think.👇🏼 https://lnkd.in/e_GBNXTv I will post a link to an automation guide of my talk as comment. In this blog post you can also find the slides. ✅ #a11y #FrontendDevelopment #wcag #WebAccessibility

32

2 commentaren

#Technology #Tech #Infrastructure #DataArchitecture #DataDriven #DataEngineering Java News Roundup: Project Leyden Early-Access Builds, LangChain4j, JReleaser, Groovy: This week's Java roundup for July 1st, 2024 features news highlighting: the debut of the Project Leyden early-access builds, LangChain4j 0.32.0, JReleaser 1.13.0, Apache Groovy point and milestone releases and updates on Jakarta EE 11 and initial discussions on Jakarta EE 12. By Michael Redlich #DataIntelligence #DataArchitect #DataEngineer

2

API Security Test in 60 Seconds 😱 Bas Dijkstra delivered a lot in our latest episode of Test Automation Experience 🎁 🔗 To watch the full episode: https://lnkd.in/ePMnUe8Z

50

4 commentaren

This is the last sale I will do for my #Angular Change Detection ebook. The content in there is still valid 🚀 And I promise it will help you understand Angular way better. It's an absolute steal 24 - 18 = 6 € excl VAT (limited)🤑 Not up to date with signals and experimental zoneless. Angular 16 This book is special for me because it is the first piece of paid content I created for simplified courses and I'm glad I sold hundreds of copies. For anyone who has supported me in buying that book, thank you so much. It was a real motivator. https://lnkd.in/ecgVs6mg Next focus: Building/Maintaining huge #Angular codebases course.

20

10 commentaren

Being in this profession for almost 28 years, I like to think I've seen the evolution that developers go through. In fact, I've experienced it firsthand and made my fair share of mistakes. I don't think terms like junior, medior, and senior make a lot of sense anymore, though. I've seen aspiring developers whose technical skills and breadth of knowledge far exceeded those of developers with 15+ years of experience. That’s why it’s so important not to judge a book by its cover. Nonetheless, experience is something to take into account when working with developers on your team.   In general, developers fresh out of school have a lot to learn. The gap between what they are trained for, and the reality of our profession is simply too big. They'll be introduced to many new techniques, so giving them overly strict guardrails isn't prudent. Even those who are self-educated need some guidance. Over time, you'll notice that they start to question those guardrails and offer suggestions that show they’re becoming more aware of the rationale behind them.   This is the point where you need to remove the guardrails to give them more room to explore and fail safely. This is also the fun period. You'll have great discussions about why certain patterns or principles make sense in particular scenarios—and when they don’t. Ironically, I've learned that developers with 15-20 years of experience are often the most dogmatic and the hardest to work with. And obviously, those with 25 years or more know exactly what they're doing, right… Or not? 🫣 #lessonslearned #consultancy #avivasolutions #carreerpath #softwareengineering

17

💻 Curious about writing cleaner, more expressive React code? Check out my colleague Jan-Willem Klomp’s latest blog! He shares how components like Nothing, Conditional, and IfElse can simplify JSX structure, improve readability, and promote clean code practices. Perfect for boosting React app composability and ensuring production-ready components. Dive into all his tips for optimizing JSX readability here 👉 https://sowo.kr/QV4dHAGf #ReactJS #JSX #WebDevelopment #CleanCode #FrontendDev #ReactComponents #ProgrammingTips #VismaConnect

2

Resharing this as endorsement - tech compensation is *at least* bimodal, and likely trimodal (depending on your location). This article is a great read for all engineers, to help explain the market and know their worth. I saw this firsthand in my job search last year. There were local companies in the Chicago area that capped out at ~120-160k for senior roles, and then larger firms (especially in finance and tech) that reached ~180-200k. But it wasn’t until I got into interviews with large public tech companies that I saw base salaries of 200k+ advertised, and total compensations reaching from 250k to 500k and up! Gergely Orosz's articles on this topic have been a huge help to me. If I had stuck to what I saw in the local market, I would've drastically limited my options and short-changed myself. The surge in remote work has made it more possible than ever to work for some of the best companies in the world, and even with lots of return-to-office happening, there are still plenty of great and well-paying companies out there. So if you're on the market (or thinking about it), keep this in mind! 🚀

6

As a freelance developer, Python and QA Engineering are my bread and butter. Here’s why I love combining these two: Why Python? • Versatile & Easy: Perfect for writing clean, effective test scripts. • Tool Heaven: Libraries like PyTest & Selenium make automation a breeze. • Smooth Integration: Works great with CI/CD pipelines for automated testing. • Awesome Community: Tons of support and resources from fellow Pythonistas! QA Engineering in My Freelance Work: • Quality Matters: I ensure every project is reliable, secure, and bug-free. • Client Trust: Rigorous testing builds trust, leading to happy clients & more work. • Efficiency: Automated tests save time, letting me tackle more projects without compromising quality. The Challenges: • Tech Overload: Keeping up with new tools & trends can be tough. • Speed vs. Quality: Finding the sweet spot between fast delivery and top-notch quality is key. 🔗 Let’s Connect: If you’re into Python, QA, or just tech in general, I’d love to chat and exchange ideas!

6

In 2021, I tried to understand how tech compensation really works - at least in the Netherlands. I published "the trimodal nature of software engineering salaries" article. Time for an update: Back then, based on ~100 data points (and my own experience as a hiring manager,) I suspected that there are three, distinctively different compensation bands for software engineers: 1. Local companies (Tier 1) Most local businesses that benchmark to the numbers on most salary comparison sites. They usually offer close to – and sometimes slightly above – what government positions advertise for senior engineering roles. 2. Ambitious local companies (Tier 2) Startups, scaleups, and more ambitious local companies that want to hire and retain the best people, locally. 3. Companies benchmarking across a region (Tier 3). Big Tech companies, hedge funds and scaleups that hire across regions, frequently hire from abroad, and often compete with fellow Big Tech giants for talent. Curiously, the third tier (Tier 3) seemed to be missing from most public compensation data sources. Since publishing the model, I've both received lots of feedback suggesting it applies to the US, Canada, UK, Europe and many other countries. I've since then also collected far more data points, manually tagged companies by tier, and can finally confirm that yes, this model holds up when compared with actual data. Here is the longer analysis (and the stats behind this graph below) in yesterday's The Pragmatic Engineer issue. Read it here: https://lnkd.in/e7FV4gBB

708

43 commentaren

Following up on my previous post about 'Type-Safe Navigation': Sometimes, we need more than just a basic data class. In my case, I’m using something like this in the picture: This `Profile` data class includes an enum and a sealed class. 🤔 Curious about how to implement this? Check out my GitHub sample for more details! https://lnkd.in/gFE93tJh

6