@thingrex@fosstodon.org
@thingrex@fosstodon.org avatar

thingrex

@thingrex@fosstodon.org

I'm an IoT Advisor and Trainer.
I believe in quality.
I do not support "fake it before you make it".
I write about #IoT, #security, and #aws related topics.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

thingrex, to javascript
@thingrex@fosstodon.org avatar

JavaScript/Node never provided sufficient support for small devices. I spent many hours trying to make it work, but that was a dead-end.

MicroPython is a decent choice for fast prototyping (at least for some platforms), but you should use it with care in production deployments.

I have never tried Rust. There is some hype around it, but I would appreciate someone sharing hands-on production experience.

thingrex,
@thingrex@fosstodon.org avatar

@alexleduc I read about Deno ages ago but never actually used it. Does it run on esp32 and similar devices?

thingrex, to ascii
@thingrex@fosstodon.org avatar

What do you think about ASCII diagrams?

They are old-school and not readable, or would they make things easier to understand?

I can not judge as the ASCII is the natural environment for me. I have played the Dwarf Fortress and Cataclysm DDA without tilesets for way too long ;)

thingrex,
@thingrex@fosstodon.org avatar

@zstix I'm glad that you like it! I enjoy the complexity of crafting offered by that game.

thingrex, to Futurology
@thingrex@fosstodon.org avatar

"I love your content, but what do you actually offer?"

That is a question I often hear, which proves two things:

  • It makes sense to put hours into creating content.
  • I should improve the description of my services.

Believe it or not, I have already made a few attempts to express my value proposition as plainly as possible. Received questions confirm that I should do a better job in my communication.

Please let me know if the following description is clear.

thingrex,
@thingrex@fosstodon.org avatar

My Services:

  1. Advisory
  2. Projects
  3. Training

Advisory:

  1. Business case validation
  2. Transformation roadmap
  3. Implementation strategy

Projects:

  1. Requirements definition
  2. Solution design
  3. Development oversight

Training:

  1. Theoretical foundations
  2. IoT using AWS classes
  3. Practical workshops

How could I improve that messaging?

thingrex,
@thingrex@fosstodon.org avatar

That is a great point, @vsaw! I wanted to explain the value proposition on my website, but it is hidden between various details.

Any improvement suggestions are very welcome!

https://www.thingrex.com/services/

thingrex, to Futurology
@thingrex@fosstodon.org avatar

Cloud is just a single piece in the Internet of Things puzzle. IoT deployments likewise demand domain-specific knowledge and non-cloud skills to build complete solutions.

Simple IoT use cases are not headline topics. There is no way to hide the lack of business understanding and poor execution behind vague terms and buzzwords. The solution either provides business value or does not. For that reason, I am a big fan of those straightforward IoT use cases.

thingrex,
@thingrex@fosstodon.org avatar

@vsaw @jadp I agree that the name is not that important, and we should focus on the business outcomes. Unfortunately, big (consulting) companies pushed the IoT conversation into the buzzword territory without providing any real value. That led to failed PoCs and unsatisfied customers/users. Luckily, the hype is over, and we can focus on solving real challenges.

thingrex,
@thingrex@fosstodon.org avatar

@Jeremiah @jadp I am not against the cloud. That is just a tool that provides value when used appropriately. For my customers, I position the cloud as the "infinite processing and storage capabilities." It is not the ultimate solution, but IoT deployments benefit from it.

thingrex, to Futurology
@thingrex@fosstodon.org avatar

MQTT is an OASIS standard messaging protocol for the Internet of Things (IoT). It is of the most popular protocols in the Internet of Things domain. AWS supports MQTT, which is the default communication method between devices and AWS IoT Core service. But there are some significant differences between the implementation of the MQTT protocol at AWS and the OASIS specification.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • cubers
  • DreamBathrooms
  • ngwrru68w68
  • Durango
  • osvaldo12
  • magazineikmin
  • mdbf
  • Youngstown
  • slotface
  • rosin
  • everett
  • kavyap
  • anitta
  • normalnudes
  • thenastyranch
  • khanakhh
  • cisconetworking
  • modclub
  • GTA5RPClips
  • InstantRegret
  • tacticalgear
  • provamag3
  • ethstaker
  • tester
  • Leos
  • megavids
  • lostlight
  • All magazines