maramono

5 ms·

1.
by maramono 10y ago
It depends on the difficulty of the bug(s) that need to be localized and fixed. I use a wide range of techniques from simple printf's all the way to a full-blown methodology that has not failed, especially when dealing with coupled bug
2.
by maramono 10y ago
I've used it several times but the big problem with it is that once you have a nice, correct model that has been checked (and no counterexamples found), there's no way to translate it to code. This meand that your basically back o
3.
Ask HN: Your experience with a dedicated test team?
5 points by maramono 10y ago|4 comments
4.
by maramono 10y ago
IMO, first we need to solve the smaller issues, most importantly to have developers start making high-quality software consistently . There is nothing that will get solved with the current "bugs are unavoidable" mentality, which
5.
How well is Puppet tested (part 2/2)?(ortask.com)
1 points by maramono 10y ago|0 comments
6.
by maramono 10y ago
If you're already considering leaving, I would take a gamble and tell your CTO/boss exactly what you said and be honest with your employer. Who knows, maybe they trust and respect you enough to make the right changes and you'
7.
by maramono 10y ago
To produce high quality code you need to change your mindset. No tools will help you if you don't know how to use them. Also you cant simply "pass the buck" (so to speak) to tools and expect greatness. TANSTAFL. I wrote a blo
8.
by maramono 10y ago
Here's what I use to develop Mutator's [0] and TestLess' [1] GUIs: - implement in Ruby - compile to Java using Warbler/JRuby - Run as Java on any platform that supports Java. You can use javafx or swing, although javafx
9.
by maramono 10y ago
Crazy idea: stop usng mocks completely where possible, and install a formal currency process for keeping the existing ones up to date. Mocks are notorious for diverging from the code they are mocking and should be used very carefully. It
10.
Ask HN: Is there a programming language with embedded testing support?
15 points by maramono 10y ago|11 comments
11.
by maramono 10y ago
What I find interesting is that there is absolutely no mention of the word 'test' in the spec. With unit testing and TDD/BDD so ubiquitous now, perhaps new languages should be created with testing support baked in instead of
12.
Show HN: How well is Puppet tested?(ortask.com)
6 points by maramono 10y ago|0 comments
13.
How to improve your debugging and testing skills(ortask.com)
1 points by maramono 10y ago|0 comments
14.
by maramono 11y ago
There are methods that can be applied to software that formally prove properties of software so that those pieces are free of bugs. These are called formal methods and require heavy use of math. Some of them are ASM and Z. There are prover
15.
by maramono 11y ago
TL;DR: Matt Wayne (the interviewee) talks about a basic problem that agile was supposed to solve: creating software that actually satisfies business requirements. For him, Cucumber and BDD solves this problem. But for all other bugs and co
16.
by maramono 11y ago
Nice title! And a related article: http://time.com/3933976/myths-fourth-of-july/
17.
by maramono 11y ago
>> A "hybrid" solution may work well for you—group your tests into small sets, then run the sets sequentially, doing as much of each set in parallel as possible. Very true. In fact, the Ortask scheduling engine takes this ap
18.
by maramono 11y ago
Related: great article on code inflation https://www.computer.org/cms/Computer.org/ComputingNow/issue...
19.
by maramono 11y ago
Very interesting! I assume that most of the smells that are introduced with new files is due to the experimentation that developers perform to solve the problem at hand. Then once a problem gets solved and the solution implemented, it'
20.
by maramono 11y ago
I can strongly relate to this experience too. As the founder of Ortask, my company is not successful by Silicon Valley measures, but it is successful in my terms because it makes me very happy. For example, I’ve learned so much by deploying