Do you offer Design Services to others? Chris Gammell tells us about his experience and gives us his thoughts on Design-For-Hire, plus other news.
View in browser
newsletter-header-nov16

TOP OF MIND

Design-For-Hire

image (1)

I spend a lot of time thinking about the folks that offer design services to others. I came from that space as a lowly one-person consultancy (dev shop? product development firm? what do we call these things?). Challenges with offering opinions and expertise for money meant some days I felt on top of the world, and on other days, I would feel lost, trying to find a solution for my clients as best I could. I joined Golioth because they were solving the exact problem I faced as a hardware consultant: How do I connect my beautiful hardware to the cloud? And what does that unlock for my clients?

 

One of the key points in the design-for-hire game is that you need to understand your area of expertise well and deploy that knowledge confidently. That starts to get tough for IoT / connected products. Every day, there’s a new communication protocol, web technology, component, or other efficiency that could save your client money and make your dev shop look better. How do you stay on top of your game when doing so means you’re giving up dollars deploying the knowledge you already have?

 

That’s why Golioth stays on top of technology changes, maintaining an active blog, and why we partner with silicon companies in order to better prepare you for the future (hint: there are some great products coming soon). It’s why we offer free training and continue to improve it. We shift with the industry so you can too. We consistently improve our SDK and adjust our examples, reference designs, content, and more. We push changes frequently so you can start strong with your client designs and deliver better products faster.

 

IoT can be very challenging, and we’re here to help you cross every hurdle. The Golioth platform is designed to make you more efficient. In fact, product development firm Ovyl, was able to prototype a Thread solution 30X faster with Golioth.

 

Whether you’re a fully-staffed dev shop, or a brave solo consultant, we’d love to work with you. Golioth users often contact us for help, and we’d love to send them your way. We’d also love to create content both for you and with you, the design-for-hire virtuoso. Sign up here if you’d like to partner with Golioth on content, joint customers, new opportunities, and more.

 

Chris Gammell,

Developer Relations

devrel@golioth.io

Golioth Changelog

 

SDK ✨

  • Version 0.8.0 of the Golioth Zephyr SDK was released on November 6, 2023. Learn more here.
  • Version 0.9.0 of the Golioth Firmware SDK 1 was released on November 8th, 2023. Learn more here.

CONSOLE 🕹️

  • Improved onboarding experience for new users. Sign up to try it out.

Recent Posts

 

Learn how to use Golioth with NXP and Memfault, Nov 14

     Authored by Chris Gammell

 

Instantly recreate sophisticated IoT designs with Follow-Along Hardware, Nov 7 

     Authored by Chris Gammell

 

Our final free Zephyr training of 2023 (November), Nov 7

     Authored by Chris Gammell

 

Automatically Detecting Boards for Hardware-in-the-Loop (HIL) Testing, Oct 31

     Authored by Mike Szczys

    IoT News

     

    Smart traffic management spending to increase 75% by 2028

     

    Supply Chains Reach Turning Point With Chip Availability

     

    Nordic nRF7002 EK Adds Wi-Fi 6 Capability to IoT Prototypes as an Arduino Shield

     

    From the Community

    1. Recently a community member asked us, “Where can I report a security issue?”

     

    All security issues can be reported to security@golioth.io. Once a security issue is reported, replicated, and resolved, we’ll send an update to the reporter and anyone who might be impacted by the issue.

     

    2. Another recent question we were asked was, “Can I Store Wifi Credentials After OTA Update?”

     

    One of the features of the SDK is that it persists credentials in Non-Volatile Storage 1 (NVS) instead of baking it into firmware. It’s a much better security practice as well as more convenient, like you say. If you follow the golioth_basics 4 example it should be using NVS in that way.

    Upcoming Events

     

    Nov 16 | WEBINAR

    Bringing Observability and Device Management to IoT Devices

     

    Nov 29 | TRAINING

    Zephyr November Online Training

     

    Jan 24 | TRAINING

    Zephyr January Online Training

     

    Most Popular Content

     

    Program your microcontrollers from WSL2 with USB support

         Authored by Jonathan Beri

     

    How to Configure VS Code for Zephyr Development

         Authored by Mike Szczys

     

    Debugging Zephyr for Beginners: printk() and the Logging Subsystem

         Authored by Mike Szczys

    Have questions? Chat with us! Join our Discord community or check out The Golioth Forums!

    Website
    LinkedIn
    Twitter
    YouTube

    Golioth, Inc., 548 Market St, PMB 73345, San Francisco, CA 94104, USA, (650) 550-1953

    Unsubscribe Manage preferences