SShortSingh.
TopTechnologyAI & MLStartupsProgrammingScienceBusinessFinanceCrypto & Web3World
Back to feed
Programming

Arquitectura de una casa inteligente con ESP32 y AWS: las piezas y cómo encajan

0
·3 views

Publicado originalmente en iot.gripe, como parte 1 de la serie "Domótica con ESP32 y AWS desde cero". La mayoría de tutoriales de domótica con ESP32 terminan en un LED que se enciende desde el celular. Los problemas aparecen después: cuando tienes diez dispositivos, cuando otra persona de la casa quiere usarlos, cuando quieres controlarlos por voz o cuando un corte de luz desordena todo. En esta serie construimos, paso a paso, un proyecto de ejemplo de domótica con ESP32 y AWS. Cada parte explica una pieza (firmware, nube, app o seguridad) con código mínimo y nombres genéricos, para que la ada

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Our brand voice rules are unit tests, including the one that bans the em dash

Nakodo (nakodo.app) has 63 hand-written search pages: guides, four free calculators, per-niche pages for YouTube, TikTok and Instagram, audience pages, blog posts and competitor comparisons. They are not CMS entries. They are TypeScript objects in src/content, listed in one registry. That part is not unusual. What has turned out to matter is the file next to the registry: a test suite that reads every page and refuses the ones that are thin, duplicated, mis-titled, wrongly linked or off-voice.

0 comments Read more at DEV Community
0
ProgrammingDEV Community ·

The free plan searches exactly like the paid one and hides the results, and the blurred rows are fake on purpose

Nakodo (nakodo.app) searches YouTube, Instagram and TikTok for creators that fit a brand's brief, then emails the ones that fit. The Free plan shows the best 20 of them and hides the rest until you upgrade. You can see that line in the comparison table on nakodo.app/pricing: creators shown per campaign, best 20 against all. The first implementation of that limit was wrong in an interesting way, and fixing it turned a product decision into one SQL expression and one deliberately dishonest-looking React component. Originally a Free campaign stopped searching once it had 20 good fits.

0 comments Read more at DEV Community