• 0 Posts
  • 27 Comments
Joined 3 years ago
cake
Cake day: May 7th, 2024

help-circle
  • This is a calculation that anyone should do before starting a business: is it profitable?

    If you’re genuinely serious about doing this, work out exactly what you’re offering and how long it will take you to do this for each system. Then work out what you need per hour to live, and work it through. You should now have a ballpark figure for a single customer/system. You might need to tweak it a bit to allow for bits and bobs. Practice it a couple of times on any different systems you can get your hands on. Be ready for hardware challenges like different GPUs or other hardware.

    You may need to figure out ways of making things quicker/cheaper, by doing some jobs in parallel and automating some stuff with scripts. You may end up with, say, multiple flash drives with Ventoy containing a few images and some scripts.

    Be absolutely clear about what you’re offering. It’s important for potential customers to know that Linux isn’t a Windows clone and it’s not trying to be, and it may take a little time to adjust, but also not too strong on that as to put them off.

    Like you already identified, you don’t want to be a 24hr support line afterwards. You may need to invest in some reference material to get them started, in the form of a quick reference booklet or some Peertube videos, or even just a collection of links to a hand-selected group of videos or sites that others have done.

    You may want to add extras, like data migration, but be careful not to have so many options as to confuse, and don’t offer it so cheap as to screw yourself. The data migration side is a minefield because of things like save games, settings and all sorts of obscure applications that can hide their stuff in nooks and crannies. Again, be clear that it’s only their docs and not all the other stuff. Also be clear that if they don’t opt for data migration their stuff will be gone: it seems obvious but not everyone understands that. Factor these things into your prices: when you’re advising people about the service you’re not getting systems done.

    Support could be an extra, but again be careful of pricing: this is an area you could bankrupt yourself if you get your pricing wrong.

    I don’t mean any of this to put you off at all. Running a business can be very rewarding and fulfilling, and could turn out to be the most awesome thing you’ve ever done. Depending on your commitments, you could try doing it as a side hustle to test out the market and refine your processes before diving in.

    And, most of all, good luck!




  • Absolutely. If people accept it they’ll keep doing it.

    However, if they’re departing from a straightforward price tag where prices are consistent and pre-agreed, it sounds like we’re going back to the time of bartering. Anywhere that implements this, customers should be prepared to say no at the till. They might backtrack on this when customers with a huge trolley pull up at the checkout and then refuse to pay because they disagree with the amount.


  • If by discrete ICs you mean custom logic baked into silicon, yes that’s always been expensive. I was referring to off-the-shelf ICs that cost pennies, which used to be orders of magnitude cheaper even than PICs (in the days before Internet connected fridges).

    Before the term software engineer was commonplace, electronic engineers used design circuits around off-the-shelf components, like the venerable TI 555 timer or op-amps, and design a circuit around them. To do it they’d need the datasheets (https://www.ti.com/lit/ds/symlink/lm555.pdf). Hobbyists and aspiring young engineers would buy books like this: (https://www.computinghistory.org.uk/det/14021/IC-555-Projects/), which were like O’Reilly cookbooks for electronics circuits. The equipment to program a PIC used to be way beyond the reach of hobbyists, and wasn’t necessary for manufacturers producing simple control circuits. If you look at circuitboards from that time you’ll see some ICs with pins that aren’t connected to anything because those just weren’t needed for the circuit, much like you describe the empty sockets in modern boards.

    It absolutely was possible in the pre-Internet days to design a fully functional fridge, and more, without writing code of any kind, and it was cheap too.







  • I’ve often thought that we could polarise the headlight glass one way, and then windscreen glass the other. The glare off the road would still hit you but the lights themselves would be much darker, but still enough for you to see they’re there. The day-runners in the corners could still be unpolarised so you’d still see the vehicle. It’d be a bit more expensive and require collaboration between the manufacturers which are probably two large reasons why it would never happen.

    I’m sure solving this problem isn’t beyond the wit of humanity, but is beyond the expense threshold that the oligarchs will tolerate from their dividends.



  • I’m pretty sure that’s a myth, but the analogy is still useful to get the concept across. It simultaneously amuses me and disappoints me that so many humans can be aware of this effect and still not recognise it happening to them, whilst the frogs aren’t actually that stupid and jump out of the water.





  • foo@feddit.uktomemes@lemmy.world•Every app in 2026
    link
    fedilink
    arrow-up
    13
    ·
    5 months ago

    Yes, you’re absolutely correct! More AI would help keep Lemmy fun – and informative – and increase engagement. Would you like me to show you how to integrate your current service with Lemmy? Just type “Yes” and I’ll give you simple and easy to follow instructions.