Sign in to view Martin’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Martin’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sydney, New South Wales, Australia
Sign in to view Martin’s full profile
Martin can introduce you to 10+ people at Betashares
Join with email
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
1K followers
500+ connections
Sign in to view Martin’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Martin
Martin can introduce you to 10+ people at Betashares
Join with email
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Martin
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Martin’s full profile
or
Already on LinkedIn? Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
About
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Articles by Martin
-
Management and leadership
Management and leadership
I'm now in the enviable position of being between jobs. People of my ilk spend this time authoring think pieces or…
6
Activity
1K followers
-
Martin Matusiak shared thisMartin Matusiak shared this🏅 3rd time's a charm, or so they say! Nearmap has been selected by an expert committee from over 800 geospatial companies for the Geoawesomeness ‘Global Top 100 Geospatial Companies’ list of 2023… for the 3rd consecutive year. Thank you to our amazing team members and customers for their support in helping us again be included in the #GlobalTop100Geo 🙏 We are proud to be a part of the passionate and innovative geospatial sector, along with the other companies also recognised in the Top 100: https://lnkd.in/eSptRWaJ #Nearmap #Geospatial #GIS #LocationData #AerialImagery
-
Martin Matusiak shared this18 months ago I moved to Sydney to start a new chapter of my life. Want to join my team? We build a Platform as a Service for Atlassian. https://lnkd.in/gaZHeH9
-
Martin Matusiak liked thisProud to be part of the Dutch startup ecosystem! Thank you Robert Gaal for the marvelous initiative! And thanks to Wesley Verhoeve, such an honor to be photographed by you.Martin Matusiak liked thisMeet Hossein Kazemi, Co-Founder & CEO at Xeco Labs: Building solutions for the Wealth Management industry. Organizes Founders Boxing Club. University of Amsterdam alumnus. What should the Netherlands do to make startups more successful? "Stimulate the ecosystem. Take startups seriously. Government should become an actual buyer of local tech." Part of the Vliegwiel portrait series, highlighting 100 Dutch founders and ecosystem builders. Photography by Wesley Verhoeve, assisted by Joseph Frank and Simón Ducos.
-
Martin Matusiak liked thisMartin Matusiak liked thisLast week, I had the privilege of being part of DevDay Da Nang 2025, where I joined the opening panel discussion on "AI-Powered Innovation: Accelerating Software Development and Industry Transformation" and also led a workshop on "Building AI-Powered Solutions: Balancing Performance, Cost, and Scalability." This year marked the 10th anniversary of DevDay, and it was truly inspiring to see more than 3,000 attendees — from students and recent graduates to experienced tech professionals and business leaders from both Vietnam and overseas. The energy, enthusiasm, and sense of community were incredible. It was a fantastic opportunity to connect with others working in tech across Da Nang and to engage with the innovative companies shaping the local and regional tech ecosystem. A huge thanks to the organisers for running such a well-executed and impactful event. I’m definitely looking forward to being part of it again in the future.
-
Martin Matusiak liked thisMartin Matusiak liked thisI've put together a list of the top 15 most-watched #Rust talks of 2024 so far. Read on 👇 1. "Filesystem in Rust - Kent Overstreet" ⸱ https://lnkd.in/eBwER6aZ ⸱ +100k views ⸱ 09 Jul 2024 ⸱ 00h 35m 16s 2. "Jon Gjengset - Towards Impeccable Rust" ⸱ https://lnkd.in/eYRSfUMt ⸱ +31k views ⸱ 03 Apr 2024 ⸱ 00h 55m 59s 3. "Christopher Biscardi - Bevy: A case study in ergonomic Rust" ⸱ https://lnkd.in/eFqt6ajh ⸱ +16k views ⸱ 11 Apr 2024 ⸱ 00h 54m 25s 4. "Nicholas Matsakis - Rust 2024 and beyond" ⸱ https://lnkd.in/e_Dymg6B ⸱ +14k views ⸱ 05 Apr 2024 ⸱ 00h 33m 48s 5. "Rainer Stropek - Memory Management in Rust" ⸱ https://lnkd.in/erpK-cJ4 ⸱ +12k views ⸱ 26 Jan 2024 ⸱ 00h 59m 48s 6. "Luca Palmieri - Pavex: re-imaging API development in Rust" ⸱ https://lnkd.in/eVCaPSiM ⸱ +10k views ⸱ 04 Apr 2024 ⸱ 00h 49m 53s 7. "Through the Fire and the Flames - Jon Gjengset | #EuroRust 2024" ⸱ https://lnkd.in/ebQxVbz9 ⸱ +10k views ⸱ 01 Nov 2024 ⸱ 00h 31m 09s 8. "Lars Bergstrom - Beyond Safety and Speed: How Rust Fuels Team Productivity" ⸱ https://lnkd.in/eb_JapYB ⸱ +10k views ⸱ 03 Apr 2024 ⸱ 00h 22m 19s 9. "Ben Wishovich - Full Stack Rust - Building Rust Websites with Leptos" ⸱ https://lnkd.in/edKArANP ⸱ +10k views ⸱ 11 Apr 2024 ⸱ 00h 44m 54s 10. "Carl Kadie - 9 Rules for Creating (...) Data Structures - Rust Linz" ⸱ https://lnkd.in/ewxjnKV2 ⸱ +9k views ⸱ 26 Jan 2024 ⸱ 00h 34m 42s 11. "Andre Bogus - Easy Mode Rust" ⸱ https://lnkd.in/ePr4BSHJ ⸱ +8k views ⸱ 04 Apr 2024 ⸱ 00h 37m 44s 12. "Rust Vienna Jan 2024 - Serverless Data Pipelines in Rust by Michele Vigilante" ⸱ https://lnkd.in/eseKjF-p ⸱ +6k views ⸱ 28 Feb 2024 ⸱ 00h 41m 02s 13. "Project Syn - Simon Gerber - Rust Zürisee March 2024" ⸱ https://lnkd.in/eAX9eX8z ⸱ +5k views ⸱ 11 Mar 2024 ⸱ 00h 29m 50s 14. "Diplomat - Idiomatic Multi-Language APIs - Robert Bastian - Rust Zürisee March 2024" ⸱ https://lnkd.in/et8BeJnt ⸱ +5k views ⸱ 17 Mar 2024 ⸱ 00h 15m 33s 15. "Massimiliano Mantione - Object Oriented Programming, and Rust - Rust Linz" ⸱ https://lnkd.in/e5Pwc6Mf ⸱ +5k views ⸱ 26 Jan 2024 ⸱ 00h 27m 38s I built this list as a part of Tech Talks Weekly. Tech Talks Weekly https://lnkd.in/eXtr7zgf is a free weekly email with all the recently uploaded talks from +100 software engineering conferences. Join thousands of readers who stopped scrolling through messy YT subscriptions and reduced FOMO. Easy to unsubscribe. No spam, ever.
-
Martin Matusiak liked thisMartin Matusiak liked thisI am excited to be launching my Live Ethics website! Check it out here – https://lnkd.in/gSD6MTQp Philosophy - and ethics in particular - are some of my passions. Given this, I have recently(ish!) been awarded my PhD in ethical leadership. However, ethics can become a bit rarified in academic institutions, a bit detached from our everyday life, when in fact ethics is imbued in almost everything we do. In organisations, ethics is often viewed through the lens of compliance or governance. These aspects are important, but not the only way to make your organisation a humane and inspiring place to work. I can help leaders in organisations make more informed and considered decisions, whether this is through ethical leadership review, coaching, workshops or advice on a project specific to your organisation. Let me know if this is of interest and you want more information!
-
Martin Matusiak liked thisMartin Matusiak liked thisSince July 1st I am the Deputy Executive Dean of the School of Mathematical and Computer Sciences at Heriot-Watt University, a role that I will be combining with my role as Head of Department of Computer Science.
-
Martin Matusiak liked thisThe 2nd AWS service I’ve launched. The 1st one was Amazon WorkMail.Martin Matusiak liked thisMake end-user devices work for your bottom line.🔒💻💰 https://go.aws/3RiznHE Amazon WorkSpaces Thin Client reduces end-user computing cost & helps improve security posture—ideal for task workers, customer support teams, & BPOs. Get safety, #CloudSecurity, & savings with #AWS #EUC. #AWSreInvent
-
Martin Matusiak liked thisMartin Matusiak liked thisOver the past 12+ years, Betashares has helped Australian investors progress their financial goals by democratising investing, expanding choice and lowering costs. Today, we are excited to announce our plans to bring our ethos of innovation, client focus and education to the Australian superannuation industry. Betashares has reached agreement to acquire Bendigo and Adelaide Bank’s superannuation business, as the first step in our long-term vision to expand beyond ETFs into the broader financial services sector. We’re privileged to serve over one million investors and their financial advisers today, and we’re looking forward to helping more Australians achieve their wealth creation goals. The planned acquisition is subject to regulatory approvals and is expected to complete in 2024 Read more here: https://lnkd.in/g5AypVdb
Experience & Education
-
Betashares
********* ******** ********
-
*******
********* ******** ********
-
*********
****** ******** ********
-
******* **********
****** ** ******* ******** ********** undefined
-
-
************* ********** *******
******** ** ******* ******** ***********
-
View Martin’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Volunteer Experience
-
Coach
Django Girls
- Present 10 years 8 months
Education
Django Girls aims to bring more women into the world of technology by organizing a free one-day programming workshop for women. It's a non profit and open source initiative open to women of all ages.
I served as programming coach at the editions:
- Groningen - September 2015
- Bordeaux - November 2015
- Rome - December 2015
- Bordeaux - April 2016
- Florence - April 2016
- Sydney - March 2017 -
Teacher
Buurthuis De Mussen
- 3 months
Education
Buurthuis De Mussen is a community center in Schilderswijk, Den Haag that organizes a variety of events for children and adults.
During my sabbatical I taught basic computer skills to a class of adults.
Languages
-
English
Native or bilingual proficiency
-
Norwegian
Native or bilingual proficiency
-
Polish
Native or bilingual proficiency
-
Italian
Professional working proficiency
-
Dutch
Limited working proficiency
-
French
Limited working proficiency
Recommendations received
10 people have recommended Martin
Join now to viewView Martin’s full profile
-
See who you know in common
-
Get introduced
-
Contact Martin directly
Explore more posts
-
Sam Taggart
SAS Workshops • 3K followers
The better you know the basics the more advanced you are. Flashy tools only work if you actually know what you are doing with them. Handing a 16 year old a Ferrari race car is probably a bad idea. Handing most software dev teams an AI agent is pretty much the same thing. You are just helping them to crash faster and more spectacularly.
9
3 Comments -
khaled nabil
Intalio • 660 followers
Everyone talks about code debt, but what about 'leadership debt'? Your seemingly innocent architectural compromises today could be crippling your team's future. Here's how to spot the invisible drag and lead with foresight. This 'leadership debt' manifests when decisions, often made under pressure for speed or immediate business value, sideline architectural robustness, developer experience, or long-term scalability. Think about approving a quick-fix integration over a well-designed API, or delaying critical refactoring because "it works for now." These choices pile up, leading to: * Stifled Innovation: Teams spend more time maintaining fragile systems than building new features. * Reduced Velocity: Simple changes become complex, error-prone endeavors. * Burnout: Engineers grapple with a constantly deteriorating codebase. Mitigating this requires a proactive approach: 1. Integrate Long-Term Vision: Always ask: "What's the cost of 'good enough' in 6 months? In 2 years?" 2. Empower Technical Leads: Give them a strong voice in strategic architectural discussions, not just implementation. 3. Quantify the Impact: Help business stakeholders understand the real cost (time, money, talent) of technical shortcuts. 4. Budget for Debt Repayment: Make technical health a regular agenda item, not an afterthought. #TechLeadership #SoftwareEngineering #TechnicalDebt #EngineeringManagement #LeadershipDevelopment #ProductManagement What 'leadership debt' have you seen accumulate in your organizations, and how did you tackle it? Share your experiences below! #TechLeadership #SoftwareEngineering
-
Sreekanth G S
M2P Fintech • 5K followers
Of all the low cost bare metal or cloud offerings, Hetzner seems to offer the best value for money, decent customer support and good ancillary offerings. Their server auctions give you bare metals at throw away price (if you don’t want great reliability - mostly for dev work, experiments or as a playground) and their cloud offers pretty decent stability (maybe not as good as AWS/Azure/GCP but at par with many other private cloud providers). I’ve tried OVHcloud in the past, and Hetzner beats them in most areas.
23
3 Comments -
Anna Mierzwińska
CyberVadis • 910 followers
Having a boring morning at work? Why not: - create a component or a service with an LLM - ask the model to review the code **like it's never seen it before** - watch it abuse its own creation mercilessly 🍿 Seriously though, this is a great way to provide some QA for generated code. PS. Also works with human devs if you extend the gap between code creation and review.
5
-
khaled nabil
Intalio • 660 followers
Your title doesn't define your leadership. I'll share how to effectively champion significant technical initiatives and steer architectural direction without a 'Staff' or 'Principal' badge. Many of us senior individual contributors find ourselves driving critical technical vision and influencing architectural decisions without the formal 'lead' title. This isn't just about doing the work; it's about leading through influence, often from the middle of the engineering hierarchy. Here's how to effectively lead from the middle: 1. **Articulate the 'Why':** Don't just present a solution; clearly communicate the problem, the vision, and the long-term impact on the product and team. Connect your ideas to broader business objectives to gain buy-in. 2. **Build a Coalition:** Identify key stakeholders across teams and levels. Seek their input early, understand their concerns, and incorporate their feedback. Influence is built on trust, empathy, and shared understanding, not just mandate. 3. **Prototype & Prove:** Sometimes the best way to lead is to *show*, not just *tell*. Build a small proof-of-concept, gather data, and demonstrate the tangible benefits of your approach. Data-driven leadership is incredibly powerful and persuasive. 4. **Mentor & Empower:** Elevate others by guiding them through complex problems, sharing your expertise, and giving them ownership over parts of the solution. When your team thrives, your technical vision gains momentum and advocates. This approach not only drives critical technical work but also builds your reputation as a trusted, influential leader, regardless of where you sit on the org chart. It's about making a significant impact from any position. #TechLeadership #SoftwareEngineering #CareerGrowth #IndividualContributor #TechnicalVision #EngineeringLeadership #Influence What's your most impactful 'lead from the middle' story? Share your experiences below! #TechLeadership #SoftwareEngineering
-
Arnoud ten Hoedt
Adyen • 710 followers
Staring at the screen this afternoon, waiting for my gitlab pipelines to turn green. My brain can't deal with the pause and it jumped back to a video I saw a few weeks back on General Agent's Ace. The video has been bugging me for a few weeks. Not necessarily a full-blown existential crisis, but it did raise the question; are we building our web portals completely wrong? If the next generation of AI tools can scrape screens and perform complex tasks across multiple products, websites, tools without a sweat, what does that mean for how we build them? The thought is very very tempting: could we not just sacrifice UX for raw speed? Do we even need quality interfaces? If AIs like ChatGpt and Gemini can understand our gibberish prompts, surely newer AIs can handle a clunky UI. But the idea falls apart the second the AI fails and a real, stressed-out human has to jump in to save the day. Preferably without being forced onto some hostile, machine-first interface. This leads to the real question; UI vs API. Or is that the wrong way to think? Instead of building separate machine-only APIs, what if we focused on making our UIs pleasant enough for humans, but boringly predictable for machines? Essentially, treating the UI as the API? Thinking like this would change a lot. Instead of the popular, but very “dry” OpenAPI specs; Could well-defined UX patterns become the next specification language, understood by humans and AIs alike? Perhaps. But it points to a more immediate reality: the concept of accessibility is getting a massive redefinition. For years, we've seen accessibility as a way to support human users with different needs. Now, AI agents are becoming a new class of "user" that relies on the exact same principles. A clean, semantic UI that’s clear to a screen reader is also perfectly clear to an AI agent. The business case for accessibility is suddenly no longer just about inclusion; it's about enabling automation. This feels like a shift. I'm curious to hear other perspectives. Are we about to see a renaissance for accessibility, driven by the needs of AI? What does "designing for everyone" mean when "everyone" now includes machines?
31
15 Comments -
Paddy O'Donnell
Confused.com • 843 followers
I was suggested a post on here trying to define the differences between DevOps Engineers, SRE, Cloud Engineers and Platform Engineers for people new to IT. It was pretty bad to be honest, overly simplistic and reductionist without any of the context around the positions, basically boiling them down to Pipelines, Monitoring, Infrastructure and reusable stuff. The comment section was a complete mess but one comment stood out to me defending the post saying "That these distinctions matter for division of labour." That's sat with me since I've read it. In an industry where we've stripped these titles of their original context do any of them actually matter? #SRE #DevOps #PlatformEngineering
8
2 Comments -
Alexander Melnik
PandaDoc • 1K followers
We recently automated our test coverage process using Claude Code agents. The key was building two specialised agents - one for writing tests, one for reviewing them - rather than using single-prompt generation. I wrote up the technical implementation, including: - How agent descriptions trigger task routing - Why tool configuration matters - The 4-step iterative process we use - Lessons learned from implementation Full breakdown here: https://lnkd.in/dgCM8XEu
11
-
Daniel Voina
Visma • 672 followers
October learnings: 1. Some tasks that used to take quite some time a few years ago are now getting done fast because the tooling evolved. When I have to parse something my usual tool was ANTLR which is great. However the scaffolding for an ANTLR is quite heavy so I found alternatives that made my work quite simpler. Recently I wrote a transpiler and after some iterations on the tooling I landed on peggy.js (https://peggyjs.org/) that is based on PEG formalism. Worked nice with JS, not so nice with TS. 2. One of the things we are missing with agents and AI is the lack of true inferences. When looking at the MCP mess (Why tools are tools and why synthetic tools?) we can see that there is a need to add some kind of ontologies over the marsh of concepts in MCP. Kind of what RDF/OWL was in the early web era. But nowadays people forget about semantics and just jump in the form bandwagon... 3. People started to observe that in fact Svelte's ecosystem is larger than React's, hence the long standing argument against Svelte is not holding anymore. Svelte, that doesn't use VirtualDOM, accommodates any other JS/TS library without any adaptations. It's 'plug&play'.
9
-
Fabian Nonnenmacher
ThoughtWorks • 474 followers
Executable ADRs? That directly resonated with me when watching Ben's "This Week in AI" stream. We’re basically talking about architecture fitness functions. I totally see good software engineering practices becoming more relevant than ever before. (Actually, quite the opposite of what "vibecoders" pray 😬) We have to think about fitness functions in a completely new light because AI shifts the cost-benefit scale fundamentally. It has never been easier to implement them, and when we use them as the harness for our coding agents, their value actually multiplies. 🚀 I agree with Ben 100% - exploring this is far more exciting than polishing our markdown writing skills.
10
-
Anirudh chakraborty
Axis Max Life Insurance… • 975 followers
We log in every day. OAuth works. SAML sits somewhere in the background. OIDC quietly does its job. And yet, when asked why… we often pause. Same screen. Same button. Very different questions being answered underneath. I wrote this piece after realising how often we confuse identity with access, not out of ignorance, but comfort. If “it just works” has ever felt like enough, this might be worth reading. (Link in comments) #CloudArchitecture #EngineeringLeadership #TechFundamentals #IdentityManagement #BuildingInPublic
8
1 Comment -
Alex Hodge
ExodusPoint Capital… • 903 followers
I’m broadly positive about AI, but I think it’s worth challenging one assumption I keep seeing: that we’re waiting for intelligence to arrive before we see a real productivity boom. We’ve had plenty of non-artificial intelligence in organisations for a long time. Skilled people, good ideas, hard-won experience. The issue hasn’t been a lack of intelligence — it’s been a lack of discipline and skill in applying it. AI unquestionably makes intelligence cheaper and more accessible. That’s powerful. But lower cost doesn’t automatically translate into better outcomes if leaders still struggle to turn insight into execution. No matter how easy intelligence becomes to obtain, the bottleneck remains the same: Clear problem definition Strong operational discipline The ability to translate insight into sustained action Until those improve, AI will amplify existing habits more than it transforms results. The limiting factor isn’t intelligence. It’s the application of intelligence.
1
-
K. Hunter Miranda
Automarka Digital Marketing • 751 followers
Confused about when to use Claude Desktop versus Claude Code? Or maybe you are still just using Claude in your browser? Most people do not know the difference. That misunderstanding will cost businesses real 💰 💵 over time. Here is the simplest way to think about it: One is built for thinking. The other is built for doing. If you are using AI for strategy, content, or decision-making, you need an environment that helps you think clearly. This is where Claude Desktop and Claude.ai shine. The desktop app and browser version are designed for: • Writing and refining ideas • Analyzing information • Building strategies • Creating polished outputs like documents, presentations, and visuals It is your workspace for clarity. But when you need AI to actually execute tasks, handle files, run processes, or move work forward automatically, you need a different approach. That is where Claude Code comes in. This is your operator. It does not just suggest what to do. It helps get it done. Now here is where it becomes important for business owners. AI becomes far more powerful when it stops acting like a tool and starts acting like a team member. That is what agents really are. Think of an agent as: AI + structure + instructions Instead of starting from scratch every time, you are giving AI a role, context, and memory so it behaves like someone who already understands your business. And you can take it further. You can have multiple specialized agents working at the same time. One focused on research One on writing blogs One on onboarding new clients All moving work forward in parallel, same way like your employees do. So why does this matter? Because most businesses are only using AI to think, when they could also be using it to operate. Forget trying to write the perfect prompt. The real shift is building systems where: • Ideas are generated • Tasks are executed • Work moves forward without constant input If you are a business owner, here is the takeaway: Use the desktop app to figure things out when you are stuck. Use the terminal version to get things done and automated. Using AI is no longer the advantage. Knowing HOW to use it is. The gap between businesses will not be who uses AI. It will be how they use it. Soon, the companies pulling ahead will be the ones running multiple agents in the background to get work automated. And if you don't know how to build agents...Don't worry! I will be sharing more on how to build simple, cost-effective agents. No technical expertise will be required.
1
-
Isaac S.
Numida (YC W22) • 778 followers
I once worked for an organisation that started with people who knew very little about software architecture and programming. They wrote scripts, deployed them through screens, and relied heavily on network communication and cron jobs for scheduling. As the organisation grew, new engineers were hired mainly for their problem-solving ability, not for a specific tech stack or strong programming background. This meant we had multiple developers, each using different languages. We had scripts in Java, PHP, Python, and more — yet we still managed to work together and achieve our goals. In a way, this forced the organisation to put systems in place that supported team scaling, without even realising it. The infrastructure itself was poor, but migrating to a better-architected system later was not as difficult as expected, largely because team scaling was already in place. This is very different from how many start-ups begin. Often, they start with a very proficient developer. The infrastructure is done right early on, but because they are working solo and moving fast, little or no attention is given to team scaling. I only started appreciating this recently while taking a course on software architecture. When people talk about scaling in software architecture, most think only about vertical and horizontal scaling. What is often forgotten is that scaling has a third dimension: team or organizational scaling. Team scaling is the ability of a system and its architecture to support the growth of the engineering team without significantly reducing productivity, increasing risk, or creating excessive coordination overhead. If team scaling is not considered early, we often end up with systems that scale well technically but struggle as the organization grows. Efficiency increases at first, then plateaus, and eventually declines. This shows up as more code conflicts, larger and riskier releases, delayed deployments, communication overhead, and difficult onboarding. Fixing these issues later usually costs a lot of time and money. In conclusion, it’s important to think about team and organizational scaling from the very start, even if you are working as a solo developer. Which do you think is harder to fix later: bad infrastructure or poor team scaling?
13
-
Deepthi Talasila
Microsoft • 1K followers
RAG isn’t dead, but context engineering is the new hotness So, is RAG (Retrieval-Augmented Generation) dead now? Last May I asked that question of Douwe Kiela, CEO of Contextual AI, based on the growing hype around MCP (Model Context Protocol). Both are data retrieval mechanisms for Large Language Models, but it’s MCP that has taken all the headlines over the past year. The truth is, RAG has fallen away as a term used by developers and AI engineers. Even Kiela, who co-authored the 2020 academic paper that introduced RAG to the world, admits that a trendy new term has taken over. Stay connected for industry’s latest content – Follow Deepthi Talasila #DevSecOps #ApplicationSecurity #AgenticAI #CloudSecurity #CyberSecurity #AIinSecurity #SecureDevOps #AppSec #AIandSecurity #CloudComputing #SecurityEngineering #ZeroTrust #MLSecurity #AICompliance #SecurityAutomation #SecureCoding #linkedin #InfoSec #SecurityByDesign #AIThreatDetection #CloudNativeSecurity #ShiftLeftSecurity #SecureAI #AIinDevSecOps #SecurityOps #CyberResilience #DataSecurity #SecurityInnovation #SecurityArchitecture #TrustworthyAI #AIinCloudSecurity #NextGenSecurity https://lnkd.in/gXkFArHX
1
-
Ben Walton
4K followers
My role requires a high amount of communcation at low latency with many teams. We use Slack like many other companies to achieve this. Many of us use the split view/window activity monitor to stay on top of incoming messages and Slack has been rolling out a behaviour change to that popped out view recently. In the previous mechanics, you'd click on an item in the view and it would open that thread in the main view. There were minor rough edges with that, but it worked. You kept the view of incoming messages in the popped activity view and updated discussion threads in the main view. After the update, clicking an item in the activity view opens the thread in. the. activity. view. If you don't navigate to that discussion in the main window or open it in a new window, your activity window is now completely useless until you click back, back, whatever, to get to the activity view. Every one of my colleagues that has experienced this change has experiencd incredible frustation. Maybe this works if you get 5 messages a day, but it doesn't work in my envornment. I personally consider it unusable. I would love a knob to at least revert to original behaviour Slack. I have provided feedback directly already, but I'm hoping that a public post might solicit a shared response from other people. Not sure if user feedback was tested before this change was made, but I've yet to find a person that thinks it is positive. (My personal thoughts, not representing my employer with this post.)
23
3 Comments -
Teddy K.
Thrivent • 2K followers
If your job involves telling other people what to do (lead engineer, architect, line manager), agentic coding workflows feel natural. Defining work for other people isn't that different than defining work for an agent. In many regards it's easier. If your job involves doing what other people tell you what to do, agentic coding is fun, but you won't experience the same multiplication effect. It's harder to scale yourself, because you've never had to before, so you don't see all the opportunities.
16
3 Comments -
Joseph Allen (ジョセフ・アレン)
Rakuten • 2K followers
Monorepos? I have recently been dropped into an in-production monorepo. For anyone new to the term, it means keeping multiple projects in a single repository. There are some big wins. Sharing design systems between front-end apps is seamless. Code reuse is simple. Dependencies stay aligned and collaboration is more open. There are headaches too. Build times get heavy. Onboarding is rarely smooth. I have yet to see a README that truly covers setup. Environment variables go missing, Docker breaks, databases and Redis need wrangling. It all adds up. I have always liked Git submodules as a middle ground, but they have never really been fit for purpose. Each project should stand alone, while the monorepo should provide clear instructions for running, deploying and developing different parts of the stack. My view is that monorepos can work brilliantly if documentation stays fresh and technical debt is managed properly. In reality, most businesses struggle with both. Sometimes smaller repos that can be retired if they do not make it to production are the safer bet.
2
-
Marcus Lim
Unspend • 1K followers
There are few things as pernicious as code that is written twice. Not because such repetition is inherently bad, but because it triggers a latent desire that many engineers have - to "reduce code duplication by creating a common abstraction". I cannot count the number of times I have seen this done (or done it myself). They (I) revel in the glory of finding two similar usecases, extracting what they (I) see to be the common parts, and migrating the use sites. "Another 24 LOC eliminated," they (I) think. "I am the most efficient engineer on earth." Regrettably, in all too short a time, those two similar usecases turned out to not be so similar after all. Additional usecases, with all the attendant thorniness of the real world, get added. The abstraction changes, expands, bulges out of shape, and finally ends up being leakier than a sieve. At some point, they (I) say, "Well, I think changing requirements has made this abstraction not worth it. Let's design a new one from scratch that will fit both existing and predicted usecases, while migrating the old ones." Invariably, more new usecases crop up. Other urgent priorities arise. Expending additional resources on the migration becomes unjustifiable. Now we have two competing changed, expanded, bulging, leaky abstractions. 💀 If there's one thing I've learnt, it's to duplicate more and (prematurely) abstract less.
28
Explore collaborative articles
We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.
Explore More