Discover and read the best of Twitter Threads about #metaprogramming
Most recents (3)
A petición de @ramloarc vamos a empezar a compartir más contenido #backend
Empezando con lo que trabajo en GitLab.
¿Cómo aprendí #rails #ruby ?
La vieja confiable documentación.
Pásenle que hay mucho trabajo remoto
guides.rubyonrails.org/getting_starte…
Empezando con lo que trabajo en GitLab.
¿Cómo aprendí #rails #ruby ?
La vieja confiable documentación.
Pásenle que hay mucho trabajo remoto
guides.rubyonrails.org/getting_starte…
@ramloarc Si de verdad quieren entender el funcionamiento del MVC de Rails,
hagan una prueba creando una mountable app, que en #rails serian #railsengines
#backend
guides.rubyonrails.org/engines.html
hagan una prueba creando una mountable app, que en #rails serian #railsengines
#backend
guides.rubyonrails.org/engines.html
@ramloarc Hace 3 años, hice una prueba técnica básica,
Crear una API con #ruby #Rails y luego mostrar esos datos en un grafico de lineas.
Por acá pueden echarle un ojito
#backend
github.com/luismejiadev/c…
Crear una API con #ruby #Rails y luego mostrar esos datos en un grafico de lineas.
Por acá pueden echarle un ojito
#backend
github.com/luismejiadev/c…
There are many forms of computing hardware systems, ever more so these days with TPU (Tensor Processing Units), GPUs, Multi-Core CPUs, Parallela Epiphany cores, FPGAs, Risc-V ISA, Analog Computing, Quantum Bits, Memristors, AI, ML, Deep Neural Nets, ...
thocp.net/biographies/pa…
thocp.net/biographies/pa…
The linked paper above is one older perspective. It was written just as the age of networking was beginning and published two years before the advent of Smalltalk-80 that brought in a new paradigm of Object Oriented Programming were objects communicate via passing of messages. 
Functional Programming makes rather massive claims that it is somehow fundamentally different than the procedural programming that came before it. Both are based upon functions calling other functions with the passing of arguments as in Lambda Calculus mathematics. 🤔 Not new.
A thread on #cpp #state_machine #software_design.
Random ideas around writing an FSM library, with examples from, and motivations behind hfsm.dev, a header-only library created using #cpp template #metaprogramming with #gamedev, #embedded and #robotics in mind.
Random ideas around writing an FSM library, with examples from, and motivations behind hfsm.dev, a header-only library created using #cpp template #metaprogramming with #gamedev, #embedded and #robotics in mind.
*Reuse vs reimplement*
State machines can be deceptively complex, and, unless a trivial one is needed, a reusable framework is highly recommended.
Rolling out one's own for special needs is ok.
Otherwise - pick from a variety of existing solutions from #boost, on #github, etc.
State machines can be deceptively complex, and, unless a trivial one is needed, a reusable framework is highly recommended.
Rolling out one's own for special needs is ok.
Otherwise - pick from a variety of existing solutions from #boost, on #github, etc.
*Static vs dynamic structure*
The first important decision is whether the structure of FSM could be built/changed at runtime.
The implementation of a dynamic FSM relies on heap-allocated memory, resizable containers and pointers, all of which come at a steep perf price.
The first important decision is whether the structure of FSM could be built/changed at runtime.
The implementation of a dynamic FSM relies on heap-allocated memory, resizable containers and pointers, all of which come at a steep perf price.
