A Company of One
This is my notes on the book "Company of One" by Paul Jarvis - one of the best books on how to start and run a 1-person solo agency. If you're looking for a follow up read, this is it.
This is my notes on the book "Company of One" by Paul Jarvis - one of the best books on how to start and run a 1-person solo agency. If you're looking for a follow up read, this is it.
I’ve been using it heavily over the past few days, and honestly, I don’t understand the hype. It doesn’t feel like an upgrade it feels like dealing with an intern who’s too eager to prove themselves and ends up breaking things that were never a problem to begin with.
I’ve recently found myself digging into the state of desktop app development in Rust not as a thought experiment, but because I actually needed to ship something cross-platform and fast. And not some toy CLI or a backend service. I’m talking about real desktop UI: buttons, windows, styling, user interaction, the whole deal.
Let's dive into the slippery world of data races, a problem that creeps up when threads, those tiny units of concurrent work, clash over the same piece of data. Imagine you’re spinning up multiple threads, each one eager to reach the same target variable like kids racing to hit the last cookie in the jar—each wanting to read, modify, and update a shared value. Without proper control, this leads to chaotic and unpredictable outcomes.
Discover how to supercharge your Swift app's performance with accessor coroutines - the secret weapon for handling large data structures without the memory overhead.
Swift 5.9 just introduced something that made Rust developers chuckle - noncopyable types. It's like Swift finally admitted that Rust had the right idea all along about controlling how values get passed around in code.
Look, we've all been there - staring at a timestamp like 1703761234 and trying to figure out how to show it as Dec 28, 2023 without writing a mess of string manipulation code. Or dealing with that one PM who insists that file sizes should show as 2.1 GB instead of raw bytes.
It is more than a decade since the first iPhone was introduced. For new developers with no preconception of how CPU architectures historically evolved on Apple platforms it may look cumbersome, official documentation about this topic might namely be incomplete or obscure. The varios types of archituctures as well as their different behaviors can be quite overwhelming. Even for seasoned iOS developers, it can be difficult to figure out how to bring everything together.
The WWDC19 marked the rise of a new era in iOS development. One of the most impactful announcements was SwiftUI a new declarative UI development framework for the whole Apple echo-system. This paradigm shift had its own impact on the Swift itself and pushed it to the spaces, where many new syntaxes have been introduced like property wrappers, opaque return types, result builders etc.
Ever tried to distribute a macOS executable only to be greeted by cryptic dyld errors? You're not alone. Dynamic libraries are fundamental to modern application development, offering code reusability and faster compilation times. However, they can also be a source of frustration when things go wrong. In this guide, we'll demystify dynamic libraries on macOS and solve common deployment challenges.