Author: Dave Strickler

  • When to Outsource

    In our personal or professional lives, there’s always a time to outsource. Maybe you lack the skill to pull something off. Maybe you lack the employees to do it. Maybe you can’t spare the time, or maybe you just want to spend your time doing other things. All of these are valid.

    But often, we misjudge the task. In a blaze of confidence, we convince ourselves we can handle it. Besides, we’re under a deadline, and bringing someone else up to speed will take way too long. The rationalizations we use cement our fate..

    “There’s never enough time to do it right, but there’s always enough time to do it over”

    A better path would be to step back before doing the task and mock it up. Break it down into five to ten sub-tasks, and assign a person and a time estimate for doing each one. Remember to build in a fudge factor for unknowns. Then carefully look at each one and decide if you and your team can really handle it.

    Being a good manager means understanding the task and what it entails. And it also means knowing when you and your team need help completing it, before you’re behind schedule.

  • Don’t Build a Service that’s a Wrapper

    If you have a driving motivation for building your next service, do it! I’ll always encourage the next entrepreneur to build their dream. But before you start, consider how unique the offering is. Has it been done before but in a friction-filled way, and you’ve reimagined it? That still sounds worth it. Does your idea take it a step further in a meaningful way? Still sounds worth it. Does someone need, not just want, the product? Keep going, I’m still listening.

    Or is it just a wrapper? Something with a glossy website, but when you dig deeper, it’s really not a new idea. Something where the first few users say, “Wait – haven’t I seen this before?” Something that’s bound to disappoint: an empty fortune cookie, a concert without a band, a “Nothing Burger”.

    Look hard at your idea and decide if it’s really just a wrapper. Look really hard. Maybe it sounded like a good idea, but it’s really just a wrapper.

    Marketplaces are smarter than you think. If your great idea is really just a wrapper, put it on the shelf before you invest your time and money in something a marketplace won’t like once they see you’re just offering a layer on top of what they want.

  • Feeling Passionately about an Issue

    We all have things we feel strongly about, and the subject of these emotions runs the gamut. But it becomes complicated when we fervently believe in something but contradict ourselves. Feel passionately about Climate Change? Then you shouldn’t use air conditioning or drive a car. Feel passionately about animal cruelty? Then you shouldn’t eat meat.

    But we’re human, and life’s decisions are complicated.

    Where you sit on an issue depends on where you’re standing.

    It’s OK to feel passionate about something and not be a martyr about it. After all, only eating meat on the weekends doesn’t make you a vegetarian, but you’re already 5/7 of the way there.

  • Treat Each Customer as Your Only Customer

    I recently got a notice from a software vendor that they were raising their prices by over 3x, with 30 days notice. A quick search into the company showed a recent S-1 filing that roughly said, “We’re going to keep raising prices to extract more value out of users.”

    While that is certainly a pricing strategy, it wasn’t what I wanted to hear as a customer. So I started making plans to leave, but couldn’t find the features in another vendor’s offerings.

    So for now, I am staying with a vendor I’ve soured on. Soured not because of their product, or even because of their price. Because of how they treated a paying customer of almost 15 years. But I’ll be looking to switch because they have lost my trust.

    Treat each customer like they’re your only customer. Pay attention to them. Listen to their needs and see if you can meet them. This is how you treated your first customer, so what happened to you along the way?

  • Subtractive Solutions

    Many solutions we implement are additive: We want more customers, more revenue, more good Press.

    Subtractive solutions are just as important, but work without offering anything more.

    • Anti-spam solutions remove your junk email. They add no new emails.
    • The fence around your garden keeps the rabbits out. It doesn’t make your lettuce grow faster.
    • The Advil you take removes your headache. It doesn’t make your brain smarter.

    But I think you’d agree, having no spam makes reading your email easier, keeping rabbits out of your garden gives you peace of mind, and having your headache go away makes you think better.

    Sometimes a solution needs to subtract something before it can add something.

  • Always use the good stuff

    I recently had to do some work on my house that involved CAT6 Ethernet cables, so I looked for some modular plugs (AKA end caps), and found an old crimper to use. After over an hour of frustration in cutting, stripping, pairing, connecting, and crimping, my Ethernet tester told me the all the cables I made were faulty. In frustration, I dug deep in my tool drawer and pulled out “the good stuff” – a Kline Tools pass-through crimper and the associated end caps. Of course, these were easy to use, made the work quick and painless, and worked the first time.

    The lesson here is tried and true. If you want it done right, don’t cut corners.

    There’s never enough time to do it right, but there’s always enough time to do it over.

  • Avoid overlapping AP channels

    When building a Unifi network with APs, it’s tempting to find an open channel, free from neighboring networks, and put all your APs on that same channel, but that would be a mistake.

    Channel frequencies are, at their core, radio signals on a certain frequency. If you put to APs close enough that their radio signal can be seen by a device like a laptop, that device will jump between them endlessly. From the device’s standpoint, it sees radio signals coming from both directions, with the same SSID, and neither AP backing down – each one demands “Connect to me” over and over. The result is your device see WiFi as “unstable”, and to be sure, it is.

    A better way to do this is to look at the frequencies and pick two that, if they are seen by the same device at the same time, at least are on different frequencies. At this point, the device is still confused, but it does see two different APs – progress.

    Better still, use a minimum RSSI value to allow “hopping”. This allows the signals to overlap with different frequencies, as stated above, but now at a minimal RSSI level – typically about 70- 75 dB. Let’s say you set each AP’s minimum connection threshold to 70 dB. By taking your laptop and moving from room to room, you should move farther away from one AP (its signal value will go up in dB as it weakens), and you’ll also move closer to the other AP (its signal value will go down as it gets stronger). Somewhere in this journey, your laptop will say “I have a signal of 65db from one AP and an 85 dB from another,” and it will choose the AP with the lower dB value. This is how your laptop knows to “hop” from one AP to another. It sees one as weakening and the other getting stronger, and “hops” to the stronger AP.

    But how do you know what dB level to set the AP at? Trial and error? A good gut feel for networks? That used to work: a notebook, lots of pencil scratching, and some math. Or you can use Claude, my preferred method. Let it do the math for you, and it will tell you what to set your RSSI values to. But don’t expect it to spit out numbers instantly. It will need you to move from room to room, run some tests in each room, adjust your APs, and rinse and repeat. This is a process, but it can tune your network as well as (maybe better) than a professional network installer.

    So, in summary, don’t let the AP channel frequencies overlap unless they are well out of range of each other, and if the APs are close enough that their signals overlap, use Claude to help you adjust the RSSI values.

  • Meshing with Unifi networks

    When setting up a Unifi network, especially if it’s at home or somewhere that’s not commercially wired, it’s pretty common to run into a room where you just can’t get a good signal from the nearest wired Unifi AP. The logical next step it to put a new Unifi AP in between this room and the nearest wired Unifi AP, and configure it as a “Child” in a mesh network, also know as a repeater.

    Now, while that often magically works the first time you do it, you may be tempted to start dropping in meshed APs all over, but that would be a big mistake. To understand why, you need to back up a little and understand how UniFi’s Mesh technology works, which is similar to other manufacturers.

    Let’s use the simple example above: a wired AP and a mesh AP, connected to the wired AP via WiFi itself. While this works well, you will notice that connecting to the mesh AP gives slower throughput because your network packets are handed off through the wired AP, and the negotiation overhead translates to roughly 50-75% slower throughput. Also, each time you connect a meshed AP to a wired AP, the wired AP needs to stop and send data to the meshed AP. While this is fast, if more than one meshed AP is connected to the same wired AP, it will slow down everyone’s throughput to the wired AP.

    Think of of this way: a mesh AP with a single radio doing both jobs has to receive each packet from its parent over the air, then retransmit it to you over the air — same radio, same channel. Every bit crosses the airwaves twice, so the radio’s airtime is split between backhaul and serving you.

    Now a smart engineer would design around this with multiple radios, but that would also need some serious CPU power to handle this. Luckily, these units are on the market, although they’re not expensive.

    If you can’t get one of these new multi-radio APs, you should consider UniFi’s “AC-LR” AP. The “LR” stands for long range, and through some beam-forming tricks, they focus the same radio signal into a cone shape to achieve a stronger signal over a longer range. Think of it like yelling through a megaphone; same yell, but it sounds louder. While the spec says 600 feet outdoors, my experience has been closer to 300 feet outdoors, and 150 feet indoors. Now think about 150 feet inside a residential house – that’s a long way. I recently put an AC-LR in a loft in my house that had no other way of connecting an AP. While the throughput was only about 30-60Mb/s when connecting to this AC-LR in mesh mode, that’s plenty fast for a video call.

    In summary, don’t put any more than a single meshed AP attached to each wired AP, and try to use a new model with multiple radios. If you can’t find one of those, then look into an AC-LR.

  • Why use FindTheTime ?

    I used to use Calendly, and as a paid user, I was pretty happy with it. It worked, but one evening I thought I could create a system that would be easier to use, cheaper, and I could add features as fast as I could think of them.

    And thus, findthetime.app was born.

    At its core, it fixes a familiar problem. It allows anyone with your private calendar link to book an appointment with you. You can link it to your Google, Microsoft, or iCloud calendars, and it has features like creating buffers on either side of a meeting so you don’t have back-to-back meetings, and your day stays sane.

    And it’s only $3/month. Even cheaper if you ask Support nicely for a coupon.

    I didn’t create this to make money. I created it to help people, like me, handle scheduling issues.

    So give it a try at https://findthetime.app and see if it works for you. If you’d like any features added or have general questions, email support@findthetime.app, and I’ll get back to you quickly.

  • AI Can’t Design Code

    AI is everywhere today, but for people who want to create an application, where is it really helping?

    As a person who codes, I can’t imagine any coder not using it, just as I can’t imagine typing a text without auto-complete. For a non-coder, AI can build a prototype for you if you carefully know how to ask it.

    But will it replace coders today? No, but it will shift the way we think of them.

    Currently, AI makes it easier to create basic code, the code that creates an application menu or a form to accept data. The list of what AI can code is long, and it’s getting longer every day.

    The nuance of an application’s requirements has become much more important than the task of building it.

    But if you think coding is simply a series of tasks to complete, you’re missing the difference between a mechanical engineer and a 3D printer. Humans envision the design and the interaction with an object, and the 3D printer just builds it. AI can be used as a tool for building applications, but it’s just that—a tool for building, not an architect.

    Today’s AI lacks higher-level tasks such as architecture—the application’s overall design. The nuance of an application has become much more important than the task of building it. While AI will get better at this, its overall design today is to regurgitate patterns that humans have already used, not to think of a clever new way of doing things. For the moment, that’s the exclusive domain of humans.

    In the near future, I see the market for a coder who can only “code” shrinking. But for application architects and designers, the market is already exploding. They are becoming the “Prompt Engineers” of our future. They’ll be good at coaxing AI to build what they envision.

    So when you hear, “AI will eliminate coders!”, that’s a gross generalization. A better explanation is that it will alter how coders do their work, recasting them as deep thinkers of the problems presented to them. They will spend more time designing at the whiteboard and less time coding at the keyboard.

    After all, what is an application but a representation of what it’s architected to do?