Michel de Graaf

GitHub’s CoPilot beta which searches your codebase is quite disappointing and inspiring at the same time. A typical dialogue goes Me: „explain the exact steps to create an invoice“ CP: „I can only answer coding questions“ Me: „explain the exact steps to create an invoice in the code“ CP: Pretty good explanation Me: „ok you mentioned that configuration pulling the strategies. What are those strategies?“ CP: „I can only answer coding questions“ Me: „… in the code“ CP: Explains the strategy configuration of the test environment And so on… it has its bright moments where you think: Documentation will be SO superfluous. Onboarding will be THAT easy. And then you realize you have to be pretty senior to handle those answers, second-guess them, and always check fact-check them. I love this, because we’re getting to play with all the potential. I guess in a few years this will be table stakes, but today there’s SO MUCH to discover!

12

6 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

That's Pieter Levels. The guy who created a bunch of lucrative start-ups that are generating him $3M/year. Did he use Angular, React or Vue? No, just good old PHP, HTML, CSS and jQuery. No fancy design patterns or architecture either, just inline code. Did he use some fancy IDE? No, wrote all using Sublime text, recently switched to VS Code. Is he paying $20K / month for hosting with containers and K8S? No, just $400 for a single VPS with 16 cores and 64GB of RAM. And that's for all of his apps combined. Simplicity is the ultimate sophistication. #programming #webdevelopment

1

Did you know if you use Microsoft 365 Copilot that you will get a new team member soon? This without hiring someone for your team. What will happen and what can it do? It will get the following roles: • 𝗠𝗲𝗲𝘁𝗶𝗻𝗴 𝗳𝗮𝗰𝗶𝗹𝗶𝘁𝗮𝘁𝗼𝗿: Copilot enables a more productive discussion in meetings by managing the agenda and taking notes anyone in the meeting can coauthor. • 𝗚𝗿𝗼𝘂𝗽 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗼𝗿: Copilot helps everyone get more out of chats, surfacing the most important information, tracking actions items, and addressing unresolved issues.   • 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗺𝗮𝗻𝗮𝗴𝗲𝗿: Copilot ensures every project runs smoothly by creating and assigning tasks, tracking deadlines, and notifying team members when their input is needed. I am curious what you think about these updates. I think it is a great add-on but still you will need to follow along to overcome mistakes or things that did not end up well in the notes. Let me know what you think about this update. If you are at the point where you want to implement Copilot in your organization and want to be sure everything is going as planned, send me a DM. All the best, Paul Keijzers [MVP] ------------------------ #Microsoft365 #Copilot #Productivity #Teamwork #Innovation

37

16 commentaren

As systems grow more distributed, choosing the right message broker becomes crucial. Let me share some key insights from my experience working with the major players: 1: No "One Size Fits All" - Kafka excels at high-throughput event streaming - RabbitMQ shines for complex routing needs - ActiveMQ is great for enterprise Java ecosystems - Pulsar offers impressive geo-replication - NATS keeps things lightweight and fast The critical decision factors I've found: 1. Scale Requirements: Consider your growth trajectory 2. Protocol Support: Check compatibility with your stack 3. Operational Complexity: Factor in your team's expertise 4. Performance Needs: Latency vs throughput tradeoffs 5. Message Durability: Data persistence requirements Start with your specific use case first, then match the technology. I've seen teams struggle with over-engineered solutions when simpler options would suffice.

285

36 commentaren

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

Working at Helin is like working in a playground for developers. The reason the job’s so versatile is this: We make a middleware edge management platform for software. I know, I know, quite the mouthful 😅 But here’s what that means… As a developer, you get to work with: → Hardware on site (computers / servers at solar or wind farms, offshore drilling rigs, etc.) → Cloud services in cloud computing platforms like Microsoft Azure And then, basically, anything in between those two. But there’s another way in which developers working at Helin get the best of both worlds. I strongly feel that, despite our extremely high levels of standard, we still remain quite flexible in how we approach projects. Our development teams: ↳ Work on short burst type project ↳ Do so in relatively small teams ↳ The work itself is quite frictionless ↳ Developers have a lot of autonomy At the end of the day, even though developers at Helin work with a full stack, there’s still this scale-up mindset. Which makes every day feel like you’re at a playground, really 😄 Looking for a new job? Send me a DM, I’d love to chat! — P.s. For those of you who are new here: hi, I’m Martijn, CTO at Helin. I share a lot of insights on what we’re doing over at Helin, building a middleware edge management platform to unlock the full potential of industrial assets. Make sure to follow me if that’s up your alley.

58

🚀 Boosting Performance with Virtualized Lists! 🚀 I recently implemented a virtualized list in React that mimics the display of 1,000 items but only renders 16 items at any given time. Instead of loading the entire list at once, I only update the visible data as the user scrolls. This technique makes the component super performant by reducing the number of DOM elements the browser needs to manage. Less DOM = less work for the browser = faster rendering! 💡 Why does this matter? Rendering large lists can lead to performance bottlenecks, causing slower load times and laggy UIs. With virtualization, we minimize the DOM nodes being processed while giving the user the feel of a large list. 🔧 Here’s how it works: By dynamically rendering only the visible items and updating their data as the user scrolls, we save memory and processing time. It’s a simple, yet powerful optimization! Huge thanks to Mohd Aman for sharing the resources that helped me dive deeper into this technique. 🙌 Perfect for improving performance in any app dealing with large datasets. 🔗 I'll share the link to the CodeSandbox demo in the comments! 💻 #React #JavaScript #WebPerformance #FrontendDevelopment #VirtualizedList #Optimization #1000Items #TechTips #Grateful

15

1 commentaar

The probabilistic Nature of LLMs: A Feature not a Bug. All you need is Validation. How a Dutch restaurant owner used AI to automate the boring things. 👨‍💻 Yesterday, I spoke at the ING & DataStax AI event in Amsterdam about applying AI in real-world scenarios. As a restaurant owner, I understand the challenges SMBs face with administrative tasks and automation. I demonstrated a POC for automated document processing, emphasizing the need of making LLMs backwards compatible with existing software systems. I concluded with a live demo, processing a set of highly unstructured (and even erroneous) invoices, contracts, and emails. More technical details in the blogpost (link in the comments). As an AI engineer with a background in hospitality and behavioral science, I use my expertise to address real-world issues. My toolkit includes chatbots, data analysis interpreters, research tools, and Github Copilot for code development. The latter crucial for lowering the entry barrier to software development by bridging the gap between human creativity and binary code using natural language. I presented after Colin Beales of Github and Jeffrey Opdam of ING, who discussed Github's Beta tools for AI augmented Coding. Michel de Ru showed how easy RAG becomes with low-code tools. Ergo: Better buckle up, because the world is about to change! AI holds the promise of bringing automation to small businesses and individuals. However, the non-deterministic nature of these systems reminds us that our current actions will significantly influence the future. To talk and learn about this from peers, I co-founded The AI Builders Club, we meet every first Thursday of the month to shape this future collaboratively. Feel free to join us! -> AI Builders Club Events: https://lnkd.in/ejQc7pUX -> Link to deepdive in the comments #GenAI #SMB #Automation #ADP #OpenAI #Pydantic #DocumentProcessing #ING #DataStax Unstract #LLMWhisperer Harrison Chase #Langsmith Jason Liu #Instructor

55

4 commentaren

𝙒𝙝𝙮 𝘼𝙡𝙢𝙤𝙨𝙩 𝙀𝙫𝙚𝙧𝙮𝙤𝙣𝙚 𝘽𝙪𝙞𝙡𝙙𝙨 𝙄𝙣𝙘𝙤𝙧𝙧𝙚𝙘𝙩 𝘿𝙞𝙢𝙚𝙣𝙨𝙞𝙤𝙣𝙨! In my experience, many people build suboptimal dimensions. I’ve previously written about avoiding common mistakes in a star schema. However, there is one optimization that many people overlook. 𝘌𝘹𝘢𝘮𝘱𝘭𝘦 There are many examples of dim's going wrong. But for this simple example we make person related dim. The data comes from multiple sources (HR, scheduling system and so on). If we remove a lot of fields to keep this example simple it looks like this: | 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲  | 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀𝗞𝗲𝘆 | 𝗡𝗮𝗺𝗲   | | HR       | 2345       | John Doe  | | Scheduling | R248       | J. F. Doe  | | E-Learning | 1D6A11A3...  | J. Doe    | Then, a decision is made about which system takes precedence and how the data is linked. For example, the linking might be done using email and the name is taken from the HR system. More complex logic is possible as well. 𝘊𝘰𝘮𝘮𝘰𝘯 𝘈𝘱𝘱𝘳𝘰𝘢𝘤𝘩 The most chosen solution is to combine data from multiple sources, resulting in one record. For instance, the HR system becomes the primary source, and additional columns and keys are filled from other systems. The result would be a table like this: | 𝗕𝗞  | 𝗡𝗮𝗺𝗲  | 𝗦𝗰𝗵𝗲𝗱𝘂𝗹𝗲𝗜𝗗 | 𝗘𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴𝗜𝗗 | | 2345| J. F. Doe | R248      | 1D6A11A3... | 𝘈𝘭𝘵𝘦𝘳𝘯𝘢𝘵𝘪𝘷𝘦 𝘈𝘱𝘱𝘳𝘰𝘢𝘤𝘩 A much better setup, however, is a table where each source has its own record. Then, additional columns and a master key are generated, and relevant fields get 2 versions. For example, the name field: one field ‘Name’ and one field ‘Source Name.’ In ‘Source Name,’ the person's name from the specific system is recorded, and in the ‘Name’ field, the name from the designated leading system is entered. This creates a wider table with the following content: | 𝗦𝗼𝘂𝗿𝗰𝗲    | 𝗕𝗞    | 𝗠𝗞  | 𝗡𝗮𝗺𝗲  | 𝗦𝗼𝘂𝗿𝗰𝗲 𝗡𝗮𝗺𝗲 | | HR       | 2345   | 2345    | J. F. Doe  | John Doe    | | Scheduling | R248  | 2345| J. F. Doe | J. F. Doe      | | E-Learning | 1D6A... | 2345    | J. F. Doe  | J. Doe       | The Name field will be mainly used in reports. However, if a user is interested in the values from each individual source, they can use the ‘Source Name’ field. This provides user insights in where to fix dataquality issues. An additional benefit is fact tables can be written with the UserID from the respective sourcesystem, without the need for a lookup to the dimension. This not only provides convenience but also improves loading speed since dimensions and facts can be loaded simultaneously. It’s important not to overdo it with the number of ‘Source Fields.’ The more such fields you add, the more space the dimension will take in the model that feeds the reports, and it can become more complex for users. However, by managing this smartly (for instance, using Display Folders in Tabular), the source fields can be available but require intentional searching to be accessed.

8

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

--- Make a positive difference. Do what you love. --- That’s why you’re working in the software industry… to contribute to something that makes a positive difference. And to do what you love. So you invested your time. Committed. It demands a lot of your creativity. Continuous learning. Keeping up. It’s challenging. And perhaps the constant high pressure is getting to you: - Sacrificing personal time and relationships in favor of work - Decline in health - Too much stress which can lead to burnout - Feeling unmotivated You never signed up for that. And you don’t know what to do about that. You were never taught how to handle tight deadlines and high pressure. In 2006, I was where you were. And I learned how to handle it through various courses and learning specific techniques. Because I was depressed and needed to know how to handle it. You can learn them too because your well-being matters more than any job. So you can keep loving what you do. And continue to make a positive contribution. It's possible to have a sustainable career without burning out. So you can be thriving and helping others with your talents. ♻️ Repost if this helped or inspired you in some way 🔔 You can follow me, Tom Verbroekken for more inspiring content like this 👇 If you'd like to get help with combatting stress or being more productive, then you can check out the link in the comments below

6

1 commentaar

Posts with images perform significantly better than posts without! Or so they say (in several studies). So I made a webapp that finds relevant free to use stock images and adds an engaging snippet of text to them, all by just pasting in the text of a post! #softwareengineering #saas

8

My "Applet Runner" plugin has reached 20,000 downloads on the NetBeans IDE. 🎉 https://lnkd.in/eJZYVrUH #NetBeans #NetBeansIDE #java #plugin #applet

16

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

Alright, it's a little behind schedule, but v4.15.0 of Nebula Logger is now available! This release brings several new features & bugfixes to the managed package (as well as few small enhancements to the unlocked package). Some of the highlights for anyone upgrading from v4.14.0 to v4.15.0: Key Features ✅ OmniStudio Logging: Built-in support to easily log from OmniStudio, a much-requested feature! ✅ Loosely-Coupled Dependencies: ISVs and consultants can now seamlessly leverage Nebula Logger without requiring it as a dependency. ✅ Enhanced JavaScript Logging: A new getLogger() function makes JavaScript logging even easier & provides improved support for logging in LWC lifecycle events Other Enhancements ℹ️ Dynamic highlights and related list components for flexipages, leveraging Salesforce's Winter '25 features. ℹ️ New list views and formula fields on logging objects, improving usability and visibility. ℹ️ Apex updates for better HttpRequest logging, async context handling, and more flexible LogEntryEventBuilder methods. ℹ️ Optimized internal performance and streamlined sf CLI commands to align with Salesforce’s latest standards. Bugfixes 🐞 Enhanced regular expressions for data masking sensitive info (e.g., SSNs). 🐞 Fixes to Apex context handling, long code snippets, and visibility rules on console tabs. More details are available in the release notes: https://lnkd.in/eBKVkfZr #Observability #Logging #Salesforce #SalesforceAdmins #SalesforceDevelopers #SalesforceArchitects #OpenSource #Apex #OmniStudio #ISV #LWC

96

7 commentaren