Cristhian

Ingeniero, Profesor, Diseñador, Músico.

[Cristhian @odcastro]

https://t.co/KQ1bDXQ7qR

[Cristhian @odcastro]

@matthewdmarsden And nobody in the World Cup (or football) cares about the USA.

[Cristhian @odcastro]

@i2cjak Why would EE people have the same opinion as a software engineer? EE is mostly physical world, and it's really early there. It's good for firmware, and makes nice simulation scripts for Matlab, etc. But that's about it for now. It won't build you a hardware system. For now.

[Cristhian @odcastro]

@matseng They worked by separating this in blocks too on the design stage and lots of old manuals have block diagrams and hierarchy. The only reason this kind of schematic exists is for maintenance and testing, and we make them nowadays too when it's needed.

[Cristhian @odcastro]

@words_salad Nope

[Cristhian @odcastro]

Remember "Prompt Engineering"? 😂

[Andrej Karpathy @karpathy]

I've never felt this much behind as a programmer. The profession is being dramatically refactored as the bits contributed by the programmer are increasingly sparse and between. I have a sense that I could be 10X more powerful if I just properly string together what has become available over the last ~year and a failure to claim the boost feels decidedly like skill issue. There's a new programmable layer of abstraction to master (in addition to the usual layers below) involving agents, subagents, their prompts, contexts, memory, modes, permissions, tools, plugins, skills, hooks, MCP, LSP, slash commands, workflows, IDE integrations, and a need to build an all-encompassing mental model for strengths and pitfalls of fundamentally stochastic, fallible, unintelligible and changing entities suddenly intermingled with what used to be good old fashioned engineering. Clearly some powerful alien tool was handed around except it comes with no manual and everyone has to figure out how to hold it and operate it, while the resulting magnitude 9 earthquake is rocking the profession. Roll up your sleeves to not fall behind.

[Cristhian @odcastro]

@lauriewired Human progress is exponential, so the earlier the better. No electronics RE tool, but a math RE one. The biggest battery smartphone (Oukitel 33Ah for example) hacked, one slowest process running a low resolution specific magical math book for transcription. Send it to Newton.

[Cristhian @odcastro]

@burkov I don't remember in the 90's reading AIMA anybody could be named expert. That was just an introductory first book to see the range of the field, but then you moved to some specific hard ones for your work, like Vapnik (if you went SVM/NN) or Sutton (if you went RL)

[Cristhian @odcastro]

@ahadj0 Yep, RTC deals with inference times, but if your problem is the later (servo local control on each motor without the total dynamics or any real time tuning of those control parameters), no AI planning model in the superior level can help with the jerkiness.

[Cristhian @odcastro]

@ahadj0 also, if your robot has a local position loop on each motor, and your model works on the trayectory level, your model will never control the jerkiness, because it's produced by local controls that work without the knowledge of the total dynamics of the robot (it's not constant).

[Cristhian @odcastro]

@ahadj0 Well of course in any control loop the sampling time (the time between each cycle of the loop) is critical, and a parameter you cannot avoid to solve from a Real Time processing stand point if you want any model to work. (1/2)

[Cristhian @odcastro]

@Birdseed501 That's the first, but the coolest is in Batman, The Dark Knight: https://t.co/OxOkZMZlcZ

[Ioannis K. Erripis @erripis]

@Birdseed501 The coolest ever depiction of skyhook (from 'The Dark Knight')
https://t.co/AHBBkRyQNn

[Cristhian @odcastro]

@lauriewired - No recursion
- No dynamic memory allocation on execution
- No use of try, catch throw. Just use return codes in functions and handle the codes.

[Cristhian @odcastro]

@IlirAliu_ This has been standard for simple automotive electronics for decades in combustion engines (very hard conditions). Usually the container is the heat dissipator, like in this little old magnetic marelli module:https://t.co/WhBVRJt7Kv

[Cristhian @odcastro]

@andrewmccalip I've used EasyEDA + JLCPCB for years now. It's just too easy when working in teams sharing the design (students love it). If you also use parts from LCSC in your design, the prototyping pipeline is complete.

[Cristhian @odcastro]

@SkyeSharkie Because doing the dishes with precision and adaptability is way, waaaaay more difficult than this. This jumping and crawling gives adaptability, but not that much precision, and you need both for doing dishes.

[Cristhian @odcastro]

@alitajran So.. we keep searching for outlook in google and then select one of the 5 first random links like always?

[Cristhian @odcastro]

@geofflangdale Because the best music business is not owning music but selling millions of guitars to millions of terrible musicians.

[Cristhian @odcastro]

@tailwiinder And it has a closed loop effect. If you use vibe coding to build the important things, vibe coding will stop working, because vibe coding runs on that important stuff ¯\_(ツ)_/¯