30 karma · joined July 9, 2015
I would not worry, though. The brain is very flexible. If you keep your mathematics sharp, you will lose less useful things like old memories instead of skills. Many professionals work in difficult jobs (say surgery) well into their 70s by keeping their skills in use.
- Oversimplified models of biochemistry (way, way more complex than insulin = fat) - Sample size of 2 trials (leaving one result) - No measure of insulin (not a one-to-one relation to blood glucose, also released in complex cycles) - No control of meal time (blood glucose varies) - No control of meal contents (assuming both meals are equal in content) - No control of fasting time (blood glucose varies)
I have had to treat diabetes in cats so I got quite proficient with measuring blood glucose levels. Even when you control every single factor as much as possible (animal eats the same amount, at the same time, every day), blood glucose varies wildly. Non-diabetics have the same massive variance, as I have done blood glucose curves to myself and to others.
This experiment is unfortunately pretty much useless. The body is a very complex organic machine with lots of parts that evolved independently of each other. There aren't neat little one-to-one relationships that can be tested easily. It is full of genes that modify genes that modify genes that secrete hormones that modify pathways and brain patterns and so on.
Since the OP comes from a JavaScript background, the static typing and low-level of Rust will be great things to learn. One also gets first-class functions that aren't insanely verbose (a problem with C# and Java 8). The structure of the game engine will also translate well to the more popular languages in game dev (C++, C#, Java).
OP, keep in mind that older languages do keep getting updated so that they stay fairly modern. In particular, Java 8, C# 6.0, and C++14. C++ especially is very common in the game dev world.
There are also several libraries with pure functional implementations (ex: bilby)
The problem is the massive, unbelievable amount of red tape to get things done. Software stacks and browsers have to get approval and re-approvals, a years-long process. Code has to be written in something stable, not something trendy. The programmers spend more time writing documents and attending meetings than coding. There are meetings about meetings and the layers of management are infinitely recursive (managers for the managers).
Start-up culture and tech trends just don't work at the scale of government, for much the same reasons massive corporations move glacially. Just add even more layers of management, congress, civil service employees that cannot be fired, and tax dollars to the mix.
I enjoyed my time working in government web, but "youth" isn't really an answer.