lgunsch

23 ms·

181.
by lgunsch 12y ago
>we need tools that make development easier, to allow keeping up with the rapidly changing requirements in the software world. The practice of Test driven development is a great solution to this. The problem is very few people use it, ma
182.
by lgunsch 12y ago
Yeah, there is a whole host of things that are left unsaid. He does a lot with TDD, and other principles like SOLID, refactoring methodology, and testing patterns that are normally associated with clean code. This topic could easily be expa
183.
by lgunsch 12y ago
It may not look better to you, but I find it works better in the sense it is actually re-usable and understandable. I have worked in microservice based architectures where the pattern (the one he started with, not the nice result) is repe
184.
by lgunsch 12y ago
I've never been with a company that didn't have serious problems with MySQL replication. At least once a month master-master replication breaks horribly and must be manually fixed; often by having to delete and remove data. MySQL
185.
by lgunsch 12y ago
He talks about "Juniors learning bad habbits," but fails to meantion what any of those habbits are. It sounds like he thinks its over engineered.
186.
by lgunsch 12y ago
That depends significantly on the language. All languages have lots of bad code of course, but I think the JavaScript community (and the language) itself promotes bad code. Or, at least un-intentionally fosters it.
187.
by lgunsch 12y ago
No, but perhaps I will take a look into it though.
188.
by lgunsch 12y ago
I have written apps in Dart, CoffeeScript, and JavaScript. CoffeeScript is a definite improvement on JavaScript, but I find it still lacks a lot compared to Dart. I still hope Dart takes off, and any new language needs at least 10 years to
189.
by lgunsch 12y ago
What really annoys me is when people throw around the term "over-engineered". This is pretty much just a complaint in disguise saying they didn't understand how it works with a 5 minute glance. If you don't have at least
190.
by lgunsch 12y ago
> Classes adds complexity and reduces composability. I could easily argue the opposite. Classes reduce complexity, and increase composability. Classes allow you to group methods in a cohesive manner into a single entity. For example, a
191.
by lgunsch 12y ago
Quote from Wikipedia article on Green Threads: "Linux native threads have slightly better performance on I/O and context switching operations." Some of the actual context switch in native threads is performed by the CPU, wher
192.
by lgunsch 12y ago
The two different threading models have different costs/benifits. Native threads are much faster at context switching then green threads, however, native threads have a significant startup cost where as spawning green threads is nearly
193.
by lgunsch 12y ago
The company I work for paid for a few licenses to use. Paying for it lets the development continue.
194.
by lgunsch 12y ago
Chrome already has somewhat of a VM. It has the NaCL, or "Native Client" which lets you run native machine code. http://en.wikipedia.org/wiki/Google_Native_Client
195.
by lgunsch 12y ago
The term "first class citizen" usually means there is a language syntax built-in for the feature that would be "first class." Dart has no such built-in syntax to deal with DOM elements. You have to use the API to manipul
196.
by lgunsch 12y ago
DOM as a first class citizen is a non-feature. Dart didn't address that feature because they went out of their way to distance the language from the DOM, and instead provide a clean API on top of the DOM.
197.
by lgunsch 12y ago
Dart is good at large applications, like 50,000+ lines of code. After 50,000 lines of JavaScript, you really start to miss static typing and hate the type system that JavaScript uses.
198.
by lgunsch 12y ago
Yes, I wrote coffeescript daily for a few months. It is also much more productive then JavaScript is, and I do enjoy it more then JavaScript, but I still find it lacking compared to Dart. Dart gives you the option of static typing. Static t
199.
by lgunsch 12y ago
I had the exact opposite experience. I was vastly more productive in Dart then in JavaScript. The code result was also more clear and understandable. I would say "readable", but often pretty looking code is as understandable as th
200.
by lgunsch 12y ago
Yeah, in my experience, "no engineering" is the most abundant; everything is thrown together willy-nilly to code as fast as possible. I have come across very few real cases of over engineering.
201.
by lgunsch 12y ago
Clean Code: A Handbook of Agile Software Craftsmanship, by Robert C. Martin.
202.
by lgunsch 13y ago
Another benefit of TDD is that it avoids generalizing by reasoning. Instead, it does generalization by example. Its not top-down, nor is it bottom-up; its programming from known-to-unknown.
203.
What TDD Is and Is Not(daedtech.com)
2 points by lgunsch 13y ago|1 comments
204.
by lgunsch 13y ago
I have also read Test Driven Development By Example. It really opened my eye's to how TDD is suppose to work. Its quite well written. Most of what I have seen on the web does not explain it to any sufficient level.
205.
by lgunsch 13y ago
James Coplien and Bob Martin have a debate of TDD and unit testing. There is a video of it on YouTube: http://www.youtube.com/watch?v=KtHQGs3zFAM
206.
by lgunsch 13y ago
Yes, I generally stick to composition. "High level" classes end up using a bunch helper classes to perform specialized tasks. I find that I do not often find the need for an abstract base class or mixins, but I will use them if it
207.
by lgunsch 13y ago
I would stick with no classes being "fat". Breaking up fat classes into many smaller classes leads to code being really easy to understand, test, and develop. I tend to stick with the Single-Responsibility-Principle and classes do
208.
by lgunsch 13y ago
Exercise - I lift weight twice a week. It really helps reduce stress, and keeps my mind sharp. Hobby: Marine Aquarium - I keep a salt water aquarium as a non-technical fun hobby. Its enjoyable, a lot of fun to build up and maintain. And its
209.
by lgunsch 14y ago
The main developer behind V8 is now the co-developer of Dart: Lars Bak
210.
by lgunsch 14y ago
I found this paper NCSU a while back: http://staff.unak.is/andy/MScTestingMaintenance/Homeworks/ST...

More ›