Aging in tech?
-
32kb effective is the least I've ever had to deal with. 4kb is rough! I agree with your comment, generally.
Real programmers use butterflies
I'm implementing a (felt) million of assembly macros for VT100 compatibility right now. Looks like the Zwölf is going to be stuck with it's serial terminal for a while longer. Before I can build a graphics card, I first got to speed up the hardware. Someone got his CDP1806 to up to 14 MHz. Now I'm curious how fast I can get my CDP1802.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
I'm implementing a (felt) million of assembly macros for VT100 compatibility right now. Looks like the Zwölf is going to be stuck with it's serial terminal for a while longer. Before I can build a graphics card, I first got to speed up the hardware. Someone got his CDP1806 to up to 14 MHz. Now I'm curious how fast I can get my CDP1802.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
overclock it and submerge it in mineral oil. That should be good for a few MHz :laugh:
Real programmers use butterflies
-
Programming tiny connectable gadgets - "Internet of Things or IoT gadgets" is an absolute joy. No frameworks to muddy the water - with 520kB of RAM you can't afford them, no abstractions to complicate the process, just you and the bare metal. Building them is fun too. But part of me wonders if it isn't because I'm getting old, and learning all these technologies feels more and more like a waste of what time I have left. I mean, I love to learn, and I love to be challenged but it has to be on my terms. In some ways, that has kept me from moving forward - designing the backend of a website these days? Get someone else - I'd be using 10 year old designs. I like these little things in a way because they're a throwback to when I learned to code. Part of me feels like I get a mulligan only I get to go back with what I know now. =) But still, the parser generators and other projects have also been newer technology avoidant outside this one particular arena. A lot of it was developed using theories that were emergent in the 1990s in computer science, so it's not a huge deal these days. I'm also struggling to wrap my head around the way people are going about machine learning. It's entirely different than how I would have and how I used to build learning systems, however unsophisticated they may have been compared to today's tech. Anyone else ever feel that way?
Real programmers use butterflies
The reason one gets "old" is due to "time compression": when you don't learn anything new, one day is just like the rest. I once said to myself I was too old to learn that (something); then looking back, after x years, it now seems is ridiculous. I've stopped thinking about where a path might lead and if I have enough "time". It only got more interesting. It's the new domains you have to learn along the way.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
overclock it and submerge it in mineral oil. That should be good for a few MHz :laugh:
Real programmers use butterflies
honey the codewitch wrote:
overclock it and submerge it in mineral oilliquid nitrogen
That should be good for more than a few MHz. :D [Liquid nitrogen-cooled AMD Ryzen 9 3900X is the new world overclocking champ | TechRadar](https://www.techradar.com/news/liquid-nitrogen-cooled-amd-ryzen-9-3900x-is-the-new-world-overclocking-champ)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
overclock it and submerge it in mineral oil. That should be good for a few MHz :laugh:
Real programmers use butterflies
Old as it may be, but at 7 MHz it does not even get warm. Passive cooling, just some conductive paste and a heat sink, will be all. Somewhere along the way the internal timing will break down, long before heat really becomes a problem. Carefully raising the core voltage will be more important to keep heat in check. For even having a separate core voltage the poor misunderstood thing was seen as an anachronism back then. The truth is that it was not outdated. It was far ahead of its time.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
honey the codewitch wrote:
overclock it and submerge it in mineral oilliquid nitrogen
That should be good for more than a few MHz. :D [Liquid nitrogen-cooled AMD Ryzen 9 3900X is the new world overclocking champ | TechRadar](https://www.techradar.com/news/liquid-nitrogen-cooled-amd-ryzen-9-3900x-is-the-new-world-overclocking-champ)
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
extra fancy! :-D
Real programmers use butterflies
-
Programming tiny connectable gadgets - "Internet of Things or IoT gadgets" is an absolute joy. No frameworks to muddy the water - with 520kB of RAM you can't afford them, no abstractions to complicate the process, just you and the bare metal. Building them is fun too. But part of me wonders if it isn't because I'm getting old, and learning all these technologies feels more and more like a waste of what time I have left. I mean, I love to learn, and I love to be challenged but it has to be on my terms. In some ways, that has kept me from moving forward - designing the backend of a website these days? Get someone else - I'd be using 10 year old designs. I like these little things in a way because they're a throwback to when I learned to code. Part of me feels like I get a mulligan only I get to go back with what I know now. =) But still, the parser generators and other projects have also been newer technology avoidant outside this one particular arena. A lot of it was developed using theories that were emergent in the 1990s in computer science, so it's not a huge deal these days. I'm also struggling to wrap my head around the way people are going about machine learning. It's entirely different than how I would have and how I used to build learning systems, however unsophisticated they may have been compared to today's tech. Anyone else ever feel that way?
Real programmers use butterflies
Maybe you should consider combining the two - make a parser generator for a custom language you design or one not available on the machine. Maybe a code generator for dealing with I/O of various flavors. I am sure you can come up with something that bridges those interests, if that is something that compels you.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
Programming tiny connectable gadgets - "Internet of Things or IoT gadgets" is an absolute joy. No frameworks to muddy the water - with 520kB of RAM you can't afford them, no abstractions to complicate the process, just you and the bare metal. Building them is fun too. But part of me wonders if it isn't because I'm getting old, and learning all these technologies feels more and more like a waste of what time I have left. I mean, I love to learn, and I love to be challenged but it has to be on my terms. In some ways, that has kept me from moving forward - designing the backend of a website these days? Get someone else - I'd be using 10 year old designs. I like these little things in a way because they're a throwback to when I learned to code. Part of me feels like I get a mulligan only I get to go back with what I know now. =) But still, the parser generators and other projects have also been newer technology avoidant outside this one particular arena. A lot of it was developed using theories that were emergent in the 1990s in computer science, so it's not a huge deal these days. I'm also struggling to wrap my head around the way people are going about machine learning. It's entirely different than how I would have and how I used to build learning systems, however unsophisticated they may have been compared to today's tech. Anyone else ever feel that way?
Real programmers use butterflies
I've always enjoyed "programming in the small". I've found it's possible to do this in any development environment if you have the mindset for it. The question you have to ask yourself is: "What's the minimum amount of code I can write that does the job?" or perhaps more to the point, _"What's the least-_engineered code I can write?" This notion is most easily expressed as things not to do. If you're thinking of acronyms like KISS[^] or YAGNI[^], you're on the right track. I always liked the notion that "every layer of abstraction is another layer of obscurity", also known as "it's frameworks all the way down". Just because you have two or more types of 'things' in your program, you don't necessarily need to create abstractions for them. I especially dislike abstraction layers that are added solely for the purpose of adhering to some arbitrary metric or style guideline.
Software Zen:
delete this; -
Programming tiny connectable gadgets - "Internet of Things or IoT gadgets" is an absolute joy. No frameworks to muddy the water - with 520kB of RAM you can't afford them, no abstractions to complicate the process, just you and the bare metal. Building them is fun too. But part of me wonders if it isn't because I'm getting old, and learning all these technologies feels more and more like a waste of what time I have left. I mean, I love to learn, and I love to be challenged but it has to be on my terms. In some ways, that has kept me from moving forward - designing the backend of a website these days? Get someone else - I'd be using 10 year old designs. I like these little things in a way because they're a throwback to when I learned to code. Part of me feels like I get a mulligan only I get to go back with what I know now. =) But still, the parser generators and other projects have also been newer technology avoidant outside this one particular arena. A lot of it was developed using theories that were emergent in the 1990s in computer science, so it's not a huge deal these days. I'm also struggling to wrap my head around the way people are going about machine learning. It's entirely different than how I would have and how I used to build learning systems, however unsophisticated they may have been compared to today's tech. Anyone else ever feel that way?
Real programmers use butterflies
I'm the opposite, willing to use 'older frameworks' as long as they get the job done. If a new project comes up, I'm always partial to do it in something familiar. I don't mind learning something new if there is a real benefit to it, but I don't have the time. A good example of this would be using WebForms/WinForms with framework 4.0. :laugh: Besides, I have 20+ years of personal code snippets, reusable code, and some code that writes code which means I can be super-productive when I need to be. :) When I do find myself having to learn a new framework (especially web) I'm reminded of how much easier it is these days (google + experience) than it was when I was learning Classic ASP in the late '90s! Anyone remember PWS on 98? :laugh:
"Go forth into the source" - Neal Morse "Hope is contagious"
-
honey the codewitch wrote:
if it isn't because I'm getting old
Join the club. None of us is getting younger, and from what I can see, most of the active CP members aren't kids.
honey the codewitch wrote:
learning all these technologies feels more and more like a waste of what time I have left.
Once you've learnt to use a few of these frameworks, you realise that they all claim to do the same thing - using the philosophy du jour. Don't get me wrong - some of these ideas are interesting, but if one has to get work out of the door, one sticks to a basic set of tools and uses them. I especially abhor the rats nest that has developed in web programming, where using one package drags in stuff from 1,001 other packages, leading to an unmaintainable mess.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
Daniel Pfeffer wrote:
from what I can see, most of the active CP members aren't kids.
A shadenfreude moment is coming. After all, who'll take care of Q&A posts as the future keeps replacing the past? I won't keep you guessing because you know what I was going to type: the current Q&A posters will share the depth and breadth of their knowledge. In fact - I'm going to make a separate post of that and then put the link right over here
-
i've found this, it's quite fresh [Swipe Gestures Using a TFT Display](https://www.codeproject.com/Articles/5287929/Swipe-Gestures-Using-a-TFT-Display)
thanks.
Real programmers use butterflies
-
> Programming tiny connectable gadgets - "Internet of Things or IoT gadgets" is an absolute joy. > No frameworks to muddy the water - with 520kB of RAM you can't afford them, no abstractions to complicate the process, just you and the bare metal. > Building them is fun too. i'd like to take part in this too. i just don't want to read (old, no time) dozen of articles to get 27 different opinions what is the best way, the economical opportunities, the future, the programming languages... if i'm not understanding the whole idea of IoT wrong, could you please point to a getting hands dirty info on the subject? what kind of device to buy and a platform that works with C or Asm and if it must be higher level can it be Lua od tiny JS 5.1? i hope one can get a job like this, away from all the: products, product offers, customers, reports...
I recommend using an ESP32 based development board. You can use Arduinos but they are more expensive and less capable, if slightly easier to work with, but that learning curve isn't a big deal. Adafruit makes the huzzah feather which i don't recommend. Hiletgo is a chinese brand I actually trust that makes a decent board and narrower than usual which makes it easier to build with on a solderless breadboard Another good one is the DOIT devkit ESP32. It's a bit wider, but all the pins are labeled, and Random Nerd Tutorials covers them explicitly - it doesn't matter a lot since they are all the same with the exception of what order their pins come in, but still. If you have one, you can code against with The Arduino IDE[^] which is C++ but C-ish in the way people actually end up using it because embedded. (mostly No STL,mostly no heap, etc) As far as getting started, just google anything "Random Nerd Tutorials" They make the best guides on how to build using these ESP32 things.
Real programmers use butterflies
-
Programming tiny connectable gadgets - "Internet of Things or IoT gadgets" is an absolute joy. No frameworks to muddy the water - with 520kB of RAM you can't afford them, no abstractions to complicate the process, just you and the bare metal. Building them is fun too. But part of me wonders if it isn't because I'm getting old, and learning all these technologies feels more and more like a waste of what time I have left. I mean, I love to learn, and I love to be challenged but it has to be on my terms. In some ways, that has kept me from moving forward - designing the backend of a website these days? Get someone else - I'd be using 10 year old designs. I like these little things in a way because they're a throwback to when I learned to code. Part of me feels like I get a mulligan only I get to go back with what I know now. =) But still, the parser generators and other projects have also been newer technology avoidant outside this one particular arena. A lot of it was developed using theories that were emergent in the 1990s in computer science, so it's not a huge deal these days. I'm also struggling to wrap my head around the way people are going about machine learning. It's entirely different than how I would have and how I used to build learning systems, however unsophisticated they may have been compared to today's tech. Anyone else ever feel that way?
Real programmers use butterflies
I struggle with this all of the time. A really big problem is people who over-architect things by insisting on chasing after the latest shiny thing or pattern, gumming up the code-base with endless libraries/dependencies and then run off to something else leaving an incomprehensible mess that has to be maintained. Add in some interfaces, code generation and various packages and many times I find myself asking: "Where is the code that actually does the thingy?" You cannot go to a controller (MVC) and find the database access code there - no, that is in a handler, but wait, it isn't there either because you've got it pushed off to EF - but the actual implementation is packed behind some generated code - and to edit that you must learn library X, Y, and Z... and it goes on and on for no real benefit.