Bart Lewis

I once asked a lead engineer on Angular: Which is better: Angular or React? His response: "Both require good engineering to be effective." So, my developer friends, consider this a reminder that "frameworks" like Diátaxis are fine, but they still require good engineering--such as UX, information architecture, style, maintenance processes, and so on--to create great documentation experiences for your customers. Alas, the framework alone isn't enough.

35

7 Comments

Haha, I got ya, you pesky pixels! One corner of my rectangle was sticking out, so I slapped a border-radius on and banished it to the ether! #cssbattle #cssgang #css

13

5 Comments

Watched a portion of the old Brian Will video on why OOP is bad (https://lnkd.in/epvfRpPR), and bombed out fairly hard when he came out with the puzzling assertion that messages between objects properly speaking shouldn't include object references. Well, there goes your visitor pattern; there goes the UI staple of registering objects with some event bus for callbacks when particular events happen. Is there some source in the literature (Alan Kay, I guess) for this odd restriction? It seems like a basic misapprehension: sure, messages should transfer representations of internal state and not haphazardly leak references to the state itself (otherwise external parties can mutate it without going through the owning object's protocol), but it's also a pretty basic affordance of message-passing systems that the addresses of things that can receive messages are first-class things that can be passed around (compare URIs in REST, or channels in pi calculus). The other odd assertion was that permitting many objects in an arbitrary graph to hold a reference to an object and access its methods was as bad as having global shared state. It fairly obviously isn't: the ability to exercise the protocol for reading or updating a particular bit of state can get passed around to wherever it needs to be, but isn't immediately available to everything, and pretty much the whole point is that you're passing a pointer to the protocol, not the rights to inspect and modify the data structures it guards. It seems that Will wants to argue for a hierarchical flow of messages down a DAG-shaped stack of routines and subroutines with a single controlling root procedure, rather than a potentially cyclic call graph with objects fielding requests from all angles. In practice that's what your average Spring Boot service actually does of course: controller to service to persistence or external client layer, and back up again. But (and this is an argument for a future post) that's because the average Spring Boot service is fundamentally procedural code, with a bit of indirection between modules. Other topologies are possible, and appropriate for particular use cases. The most generous reading I can give of Will's argument is that OOP offers more flexibility than perhaps a majority of actually existing programs really need, and we'd be happier and less burdened by object bureaucracy if we wrote those programs in a more constrained idiom. I actually think that's kind of true, but haven't got to the bottom of what it means in practice just yet.

2

Safari 18.0 has just dropped, so you can now animate the display property. Just look at this dialog/popup animation in and out. So simple 🫶 Of course, I have a post about this technique! https://lnkd.in/ecewD9Kk #css 

4

If you've ever created a plugin with JUCE, you've used the AudioProcessor class. This is one of the most important classes in the entire framework! A secret of mine is that I've never taken a look any further than the essential functions beyond prepareToPlay() and getNextBlock(). I asked questions like... ✅ What is the deeper purpose of the AudioProcessor class? ✅ What do the other functions do? ✅ How does the work we do in the AudioProcessor wrap into the various plugin formats like VST3, AU, and AAX? Join me in this exploration into answering these questions! We also talk about CMake build options and how they directly affect this class and more. This has been a game-changer for how CMake can enhance the toolkit for fellow developers. Ready to dive in? Check it out here: https://lnkd.in/ep3Vsxck

47

1 Comment

I've worked in similar environments and deploying to production several times a day takes a lot of the risk out of delivery. As mentioned here it's predicated on separating the concepts of deployment from release using techniques like feature flags and branch by abstraction.

8

It seems that Adam Argyle has a bad habit of _blowing my mind_; which happened once again this morning while I was going through the #CSS Open Props project's "built with" showcase. I noticed that Adam was using CSS Grid to control the spacing in between copy elements on the page. I've never seen this technique before; and it may have just completely changed the way that I think about margins. Read more: https://bennadel.com/4734 For years, I've been futzing around with `:first-child` and `:last-child` selectors for tweaking margins; but, such techniques are fraught with error, not the least of which is that they target DOM elements and not _rendered_ elements, which creates many "false positive" matches. CSS #Flexbox and Grid only target rendered elements (regardless of what else is in the DOM tree). This makes this layout-based technique for margin management especially exciting!

4

2 Comments

🤯 Okay, so Rob Eisenberg is a master of the dark shadow arts (CSS & JS). Because his `addGlobalStylesToShadowRoot` in this article is pure witchcraft. In the best possible way, of course. #css #javascript #webcomponents https://lnkd.in/giA6ipxE

23

1 Comment

This summer, the Go team introduced new iterators, which, naturally, stirred up some controversy. Critics argued the design wasn’t very "Go-like"—too functional, too complex, and missing Go’s typical simplicity. A common complaint was: why not just introduce an iterator interface and allow range operations over it? I get the criticism, and I agree to an extent. But the decision to go with push iterators over pull iterators makes sense too. It simplifies common tasks—like iterating over a database cursor—in a way that’s easier to write and follow than managing an iterator state machine. For a function to act as an iterator, it has to follow one of three signatures: func(func() bool) func(func(K) bool) func(func(K, V) bool) And here’s the first challenge: you end up writing a function that returns another function, which takes yet another function. It’s a bit of a nesting doll situation. https://lnkd.in/eKDdUD3D

6

As always Jörg helps AEM developers to understand why they should not underestimate the effects of their coding practices. Being aware of the logics implemented enables to really achieve best performances on any platform

17

The software testing community here on LinkedIn is appearing like the rest of social media lately. It has mostly binary opinions, and lacks empathy and respect for the context - with many saying one way is the only way. It's a shame more people are not open to being challenged across all areas of work and life. I remember a time when students were open to listen to talks that directly challenged their beliefs, now many won't accept it, so colleges and universities shy away from it. Free speech is important, as long as it doesn't violate someone else's rights (free speech doesn't allow for inciting hatred for example). Back to testing...I'm not suggesting people stop with their opinions on testing, yet it would be more effective if their binary argueing stopped, and an open conversation with various views were shared. Then we can all learn and make informed decisions. Just saying... It would be nice across all areas of life I think. Sadly social media appears to make people feel safe to do otherwise. I hope you're open to different opinions and are able to debate instead of force an argument based on a binary belief you have. #softwaretesting #softwaredevelopment #technology #whatinspiresme

10

4 Comments

There’s something for everyone in web development in here:

8

1 Comment

If I wrote a book called "Typescript, RxJs, and the Angular Paradigm," based on the ideas I write here about sticking as close to "The Angular Way" as possible, including Typescript and RxJs, how many of you would buy it? Because I might have been given an opportunity to write it.

22

11 Comments

Kyle does a great job to highlight the pains of translating a shared design system into shared styles between React web and React Native. I do like the use of types to enforce existing style primitives compared to hard coding numbers, but I understand that native mobile developers are not used to the compositional nature of the first design system, compared to shared styles via StyleSheet, NativeWind, or similar. Fusing mobile and web beyond the data layer becomes more and more tricky. react-native-web often isn't the answer. As "headless" components grow to help fuse HTML vs React Native components, we still have a need for sensible styling.

8

Being 'senior' just means I’ve failed more times. Doesn’t mean I know everything. I’ve just faced more issues and found more shortcuts. But you’d be surprised how often I still mix up `slice` vs `splice` Or need to look up git commands 🔍 Failure is how we grow 🌱 What’s something you still have to look up? #SoftwareEngineering #GrowthMindset #LearningFromFailure

71

7 Comments

Let's talk about the challenges when it comes to contracting freelancers for audio software development… A few years ago, a prospective client chose to source a developer on their own instead of using our consulting services at The Audio Programmer. Fast forward to now, and that developer has left them high and dry, taking a full-time role elsewhere. 😬 We're stepping in to help, but this could've been avoided. Here's the deal: 🔍 Companies often think they're saving money by going solo, but they risk a lot. Without proper management infrastructure, assessing a developer's ability and handling unexpected issues becomes a gamble. 🛠️ Developers, on the other hand, might not realize the extra "scaffolding" needed for solo freelancing—handling IP, invoicing, aligning expectations, and navigating communication gaps. These are just the tip of the iceberg when it comes to company-freelancer dynamics, especially in software development. For the past 7 years, we've been bridging this gap. We ensure companies get what they need, even if it means replacing developers and adapting teams. And we make sure our developers get paid and focus on what they love—writing code and creating amazing products. No one gets left hanging. 🤝 What are your thoughts on the challenges with freelancing within audio software development? Let's talk shop!

50

37 Comments

Why most dev agencies fail: They treat projects like transactions, not partnerships. I’ve tried to learn from that. We really try to keep relationships at the heart of the Minthouse It’s a different approach. Every project is a shared journey. We don't just code and disappear. We're in the trenches with founders, from idea to launch. It's not always easy, but it's always worth it. The best products are born from true collaboration.

11

2 Comments