HackerTrans
TopNewTrendsCommentsPastAskShowJobs

pitay

no profile record

comments

pitay
·5 лет назад·discuss
Not saying this is a good or bad thing, but one way to make laws not be selective is to have mandatory enforcement and mandatory sentencing required for every law. If the law could be interpreted to apply to a situation, then it does apply to a situation in this model. Laws would be very carefully written under this and extremely well specified. With this you could be much more sure that a law is applied as written, whereas at the moment you have to continually look at the results of cases and can't see when people are let off the hook because someone in an authority position is well disposed to the person because they are friends with them or for other reasons. This can happen before a case goes to trial or during the trial.
pitay
·8 лет назад·discuss
Kind of amusing that it is named after Alan Turing when one of its major features is not being Turing complete by default.

This effort for very high level code for building applications reminds me of Eve[1] as a non-traditional programming language (now not actively developed AFAIK, so more suitable for study than actual use). Both languages are designed to be accessible to people who aren't developers and making it simpler for people solving problems.

Love how Alan is trying to close the gap between requirements and actual code. At least for me, one of the things that has bugged me about writing in a language such as Java is tracing code to requirements. For Java the first thing to think of to solve this is discipline and complete documentation. I mean there are things like using a traceability matrix[2], but are there better ways to find or represent the relationship between requirements and code. There have been things commonly proposed to programmers such as Test Driven Design, but they are for making sure that the requirements are met by at least some of the code, not for tracing code back to requirements. Are there better ways to manually checking? Perhaps formal methods for tying requirements to every bit of code in a project, or anything else. Maybe languages and platforms like Alan are the way forward on this issue for a lot of things. Counterpoint, I don't know of any real effort from me or anyone I have worked near to trace code to requirements, the effort has been only to make sure requirements are satisfied, it doesn't seem to have caused any issues, so maybe it is only worth it for safety critical code.

[1] Eve: http://witheve.com/ [2] Traceability matrix: https://en.wikipedia.org/wiki/Traceability_matrix