Will Hitchcock

Why neutrality in #SoftFurnishings is harder than boldness (And why I’ll always choose it.) 1️⃣ Neutral isn’t minimal. People often confuse neutral palettes with playing safe. But designing a neutral space that feels complete takes far more restraint than going bold. It’s easy to fill a room with colours and patterns. Much harder to know when to stop. 2️⃣ It takes discipline to edit. When clients see an empty corner, their first instinct is: “Let’s add something.” My job is to pause, feel the energy, and ask, “Does the space need more? Or are we avoiding stillness?” #HealingSpaces often breathe through the things we remove. 3️⃣ Quiet choices hold deeper power. A soft textured rug or a muted sheer aren’t background details. They are anchors. They guide the way you feel, move, and think. 4️⃣ Neutrality requires deep listening. Not just to the client, but also to the space. The walls. The light. The emotional weight of what already exists. If you listen carefully, you’ll often realise: The space always says something. You just need to honour it. 5️⃣ Bold is easy, but balance is tricky. Using statement colours is easy.  It takes a calibrated mind to design a space that feels peaceful and subtle. That is what makes neutral spaces feel timeless. Not boring, but deeply human. 💬 Have you ever walked into a room and felt instantly calm, without knowing why? *********** 🏡 Follow Darsha Manek for more on Soft Furnishings. *********** #LuxuryDesign #Entrepreneurship #EnergeticAlignment #Fabrics #Trends #HealingSpaces #SoftFurnishing

13

Here’s how AI is tangibly changing how the design team at Intercom operates: 1. Designers are shipping code to fix UI bugs 2. They’re vibe coding the roadmap 3. Even stepping into owning the entire frontend More details in the thread.

110

17 Comments

The Narrative Code Contemplating how our systems tell stories: Simple state models: "This is how things are now." Event sourcing: "This is how we got here." CQRS: "Different questions need different stories." The architecture you choose shapes the questions your business can ask about itself. #softwarearchitecture #ddd #coding

3

Not Quite Micro-Frontends Micro-Frontends Part 1: How We Built a Modular Front-End that Scales Frank Visaggio and Salt Lake City .NET thanks for inviting me to present tonight. I really enjoyed everyone's thoughtful questions. If you're curious about micro-frontend solutions, here's part one of the blog post I wrote that covers what we talked about: https://lnkd.in/gMCwEJ2g

5

4 Comments

If the job of PM is to embody the voice of the customer, then explicit PM roles are less required the more your builders embody the customer directly. The inverse is also true. e.g. DevTools need less. Healthcare needs more.

3

The biggest QA problem I keep seeing isn’t execution. It’s the lack of a single source of truth. PRDs, Figma, tickets, people’s heads… scattered everywhere. Real confidence doesn’t come from running more tests. It comes from knowing what truly needs to be tested.

34

1 Comment

A very interesting take on the ethos of 37Signals (the company behind Ruby on Rails, Basecamp, Hey, ShapeUp methodology, and more). They have been doing things differently since their early days. They do a lot of things right, and this posts offers a reason why. Good read with valuable lessons. https://lnkd.in/gCe4Dj6p

13

2 Comments

Cursor just released a visual editor inside its internal browser! This feels like a real step forward for our team at Agoda as we explore how designers can safely make small frontend changes in our enterprise codebase. Here is what our workflow is shaping up to look like: 1. Spot a design issue that slipped through QA 2. Open the repo in Cursor 3. Use the visual editor in Cursor’s browser to fix the design issue 4. Commit changes and open an MR on GitLab 5. Review with devs, merge, done ✅ This gets us much closer to letting designers handle simple UI fixes without friction 🥳

37