Deputy Sheriff The Viking Programmer
https://www.oo-software.com/en/shutup10
Having Windows 10 update issues? You can strike two birds with one stone by installing Linux Libre and a compatible distro of your choice.
Forwarded from Pure & constructive mathematics in theory and use (GNU/Brett G.)
A Categorical Theory of Patches
https://www.youtube.com/watch?v=SnRFGZYo-xI
https://www.youtube.com/watch?v=SnRFGZYo-xI
YouTube
A Categorical Theory of Patches
When working with distant collaborators on the same documents, one often uses a version control system, which is a program tracking the history of files and helping importing modifications brought by others as patches. The implementation of such a system…
Forwarded from Ask GNU/Brett (Archived)
Should I attend an intensive bootcamp to study programming?
Absolutely not. Coding bootcamps are a major scam in every big metropolitan city. They are not accredited, and just want to siphon off your hard earned money.
Bootcamps:
— 12-16 weeks
— Lots of money
— Very little useful skills
— Narrow subject interest
Scheme w/ a book:
— 3 days with no experience
— 1 day with experience
— A lot of useful skills
— Broad and expansive subject interest
— Free
Absolutely not. Coding bootcamps are a major scam in every big metropolitan city. They are not accredited, and just want to siphon off your hard earned money.
Bootcamps:
— 12-16 weeks
— Lots of money
— Very little useful skills
— Narrow subject interest
Scheme w/ a book:
— 3 days with no experience
— 1 day with experience
— A lot of useful skills
— Broad and expansive subject interest
— Free
Forwarded from Ask GNU/Brett (Archived)
Imperative vs functional programming? why should I learn one over the other?
Both are useful for different reasons, but I EMPHASIZE a learning of functional programming for the following reasons. You tell me which one you think is better.
— The Development Cycle
[Imperative]
Using informal language a specification may be open to interpretation. Using appropriate testing strategies we can improve confidence - but not in any measurable way.
Mistakes/bugs are common and difficult to spot and correct.
[Functional]
Using logic we can state the specification exactly. Using mathematics we may be able to prove useful properties of our programs.
Mistakes/bugs are not common and relatively easy to spot and correct if they are not caught by a type checker.
— The Development Language
[Imperative]
Using structured programming or object oriented techniques we can reuse code. Using structured programming or object orientation we can partition the problem into more manageable chunks.
[Functional]
Using structured programming or declarative techniques we can reuse code. We can partition the problem into easy to use chunks - plus there are often "higher-level" abstractions which can be made ML which would be difficult or impossible in a traditional language.
— The Runtime System
[Imperative]
The compiler can produce fast compact code taking a fixed amount of memory.
Parallel processing is either not possible, or extremely unpredictable and unsafe.
[Functional]
Code is usually type-checked at a high degree of precision, but the memory requirements can be variable and unpredictable.
Parallel processing is easily possible and have guarantees of safety.
Both are useful for different reasons, but I EMPHASIZE a learning of functional programming for the following reasons. You tell me which one you think is better.
— The Development Cycle
[Imperative]
Using informal language a specification may be open to interpretation. Using appropriate testing strategies we can improve confidence - but not in any measurable way.
Mistakes/bugs are common and difficult to spot and correct.
[Functional]
Using logic we can state the specification exactly. Using mathematics we may be able to prove useful properties of our programs.
Mistakes/bugs are not common and relatively easy to spot and correct if they are not caught by a type checker.
— The Development Language
[Imperative]
Using structured programming or object oriented techniques we can reuse code. Using structured programming or object orientation we can partition the problem into more manageable chunks.
[Functional]
Using structured programming or declarative techniques we can reuse code. We can partition the problem into easy to use chunks - plus there are often "higher-level" abstractions which can be made ML which would be difficult or impossible in a traditional language.
— The Runtime System
[Imperative]
The compiler can produce fast compact code taking a fixed amount of memory.
Parallel processing is either not possible, or extremely unpredictable and unsafe.
[Functional]
Code is usually type-checked at a high degree of precision, but the memory requirements can be variable and unpredictable.
Parallel processing is easily possible and have guarantees of safety.