flavio81

73 ms·

691.
by flavio81 9y ago
>Remember, code reviews aren’t about nitpicking through another person’s code. Use a computer to nitpick. Trust me, they are really good at it. No, they are not good. They are good at complaining about meaningless things like braces pu
692.
by flavio81 9y ago
>If you don't mind me asking(...)how is this score calculated, how does it aggregate all your financial information without a specific identifier We do have an specific identifier. Each person has an ID card , with an ID number.
693.
by flavio81 9y ago
> Most bugs are about types, just most languages’ type systems are too weak to express the logical types relevant to many important bugs Ok, so you are writing a function for a fast approximation of ATANH using IEEE floating point stan
694.
by flavio81 9y ago
>"Checking at runtime is exactly the problem. Why would checking at runtime be more reliable than compile time?* If you use metaprogramming (i.e. Lisp macros, Scheme/Racket macros, Clojure macros), then the only way to have t
695.
by flavio81 9y ago
> Statically type languages prevent a lot of bugs Correction: Statically typed languages prevent a lot of the bugs that total beginners to programming would make; while they are useful in preventing the one, two or tree trivial, easy t
696.
by flavio81 9y ago
> The primacy of the SSN in American society is idiotic. It's a "secret" that you have to hand out to dozens of different organizations I'm not from the US. The first time i had an american friend explain me the SSN
697.
by flavio81 9y ago
> (thankfully, code printouts were already going out of fashion back in 1998, when I had that job. I can't for the life of me picture someone reading a printout today. For me, the best way to review source code is to have it print
698.
by flavio81 9y ago
> "After almost 7 years of continual improvement and refinements since OpenCOBOL version 1.1 and 3 years after the release of GnuCOBOL 1.1, the GnuCOBOL team is proud to announce the formal release of GnuCOBOL 2.2." They took
699.
by flavio81 9y ago
> I used to work with COBOL and I wouldn't wish the language on anyone. There are worse things. I'd rather work on Cobol than in PHP4, or in a project where I have to deal with front-end stuff done using JS and back-end stuff t
700.
by flavio81 9y ago
> Lisp is pretty slow in comparison to C, that's acceptable. It is not. (Common) Lisp can be made as fast as C if you really need it, by using tricks... By the way, for a while, the fastest HTTP static server was one written in Lisp
701.
by flavio81 9y ago
>However, many day-to-day developers (...) believe that Lisp's syntax creates nigh-unreadable programs (...) Very smart people will disagree with that opinion (...) it's a fact many people believe (...) trying to convince peop
702.
by flavio81 9y ago
Thanks for this! Looks elegant.
703.
by flavio81 9y ago
>C++ shows that in theory you can fix any flaw in an existing programming language as long as you maintain backwards compatibility by simply adding more features. Well, "adding more features" can't be done "simply&q
704.
by flavio81 9y ago
It is strange that the author has not included the use of Promises and the async keyword. Should be essential knowledge today. > Value vs. Reference — Understand how objects, arrays, and functions are copied and passed into functions. Kn
705.
by flavio81 9y ago
" The problem is that there aren't many other options. Google is evil, Facebook is evil, Apple is evil if you care about open hardware, Microsoft is too stupid to be evil but might at some point become evil again, and Amazon is pr
706.
by flavio81 9y ago
"Founder Vivaldi showed Wired journalists copies of the letters he had received from Google. They demanded that Vivaldi add links to the EULA (user license agreement) “within each button to download the program.” This is a rather stra
707.
by flavio81 9y ago
Does Go support macro assembler programming? It is a bit harsh to have to program assembler in a fully "write all the instructions" way, particularly in 2017... Additionally, i see that the opcodes are not machine language (target
708.
by flavio81 9y ago
> Every Programmer Should Know LISP Seriously, yes. Every programmer that wants to perform as high as possible, should grok Lisp, or a Lisp dialect. It makes sense, since they are "programmable programming languages."
709.
by flavio81 9y ago
7. 'Dilbert' is a documentary.
710.
by flavio81 9y ago
" I called the janitor the other day to see what he could do about my dingy linoleum floor. He said he would have been happy to loan me a polisher, but that he hadn't the slightest idea what he had done with it. I told him not to
711.
by flavio81 9y ago
> Very nice! If you wanted it to save to disk instead of living wholly in memory, how would you do that in C? The idea would be to map your memory space to disk space (using random access as provided by C stdlib); the problem would then
712.
by flavio81 9y ago
> Does anyone have any pointers? Sure, here you are: void *x= malloc(16384) (Couldn't resist)
713.
by flavio81 9y ago
> You can’t prove even very simple universal properties of dynamically typed code, such as “when given an integer, this function always returns an integer” Really? Straight from my common lisp (SBCL) command line: CL-USER> (defu
714.
by flavio81 9y ago
> and Python really has no infrastructure for that. Nor do any other dynamic languages like Ruby, Perl, JavaScript, Lua, or PHP, as far as I can tell. This is not correct. Common Lisp easily supports structs, and is a dynamic language.
715.
by flavio81 9y ago
> C header file mess is caused by its designers ignoring the work outside AT&T and not bothering to implement a module system. To be fair to them, they wanted to create a language whose compiler did fit into the limited hardware they
716.
by flavio81 9y ago
Your argument was that some IDE features are really really needed. > There are good reasons industry best practices include things like code reviews, testing, and staging environments. But I suppose, if you are going to ignore all of the
717.
by flavio81 9y ago
> You didn't watch the video, or you watched but didn't listen, or you watched and listened but didn't think. My post was about "discussions" and targeted to the comments that usually come whenever static typin
718.
by flavio81 9y ago
> This is just rehashing the same tired and fallacious argument that most errors aren't type errors. And it is pure fallacy because different languages have different ideas as to what constitutes a type, Ok, so you are writing an al
719.
by flavio81 9y ago
> "Static" means "compile-time checking". "Dynamic" means "defer checks to run-time" It is not really about checking , it's about allocation/binding . Static typing, for binding a varia
720.
by flavio81 9y ago
> Try reading your own code written two weeks ago. How about a month ago? Three month ago? In fact i did. Code of 8 months ago (december 2017). Easy to read, because i used named parameters extensively and added comments at every functio

More ›