I think the recommendation seems to be that all over-40 should be taking low-dose aspirin - to prevent blood clots - plus aspirin is anti-inflammatory which may work against heart disease or arterial disease which has some links with inflammation. In addition aspirin has anti-viral properties as well.
Most older people being treated for routine heart disease take low-dose aspirin - so this would be something like that.
However, consult with your doctor to see if aspirin is appropriate for you.
Saw this article today by chance:
When too much coding can kill you. | Javalobby
Julian Exenberger
When too much coding can kill you.
05.28.2014
In general programming is one of the more unhealthy occupations. Bad for the eyes to be staring constantly in one place - maybe leads to bad circulation within eye vitreous humor, bad for back, bad for circulation - blood clot dangers as suggested by mind etc.
I have often found the multiple roles that android development requires like finding ad networks, marketing etc. to be a pain - but it could be that the changing roles required - at least for the single-independent-developer - may allow some variety to the developer. However, the problem is that these usually do not come together in neat daily packages - so you may spend more time developing - and maybe later spend more time on marketing - or making the graphics etc. for the app.
EDIT: one of the reasons programming can be so dangerous is that if you are doing any type of wide change in your code - or are getting back to your code after some time - it takes a huge effort to reintroduce your brain to your code (this is even more so if you spend a major part of your day in interacting with other people or humans not related to programming etc.) - and often it means that your programming session can only start becoming productive after some time messing with the code. Often the most productive work will be done very late at night or on those nights where you pulled an all-nighter.
I think this requirement to pull an occasional all-nighter is not a programmer-specific peculiarity - but may be a requirement for certain types of programming activities - where a major reworking of code is required etc. In such circumstances, the brain needs to be in control or aware of a vast amount of code - and if you are getting back to that specific code after a long time - then it invariably needs accomodation i.e. you getting comfortable with the code - having it all in your mind etc. - and that may take some preparation - which means it is only when it is really late at night that you start to click and actually do something with the code. It also means then that you are fired then and cannot sleep until that part is done - because otherwise it will take another few hours next day to reacquaint yourself with the code etc.
