qwer

9 ms·

31.
by qwer 10y ago
> Quite false. How do you expect developers to take you seriously when you essentially say "you can't properly do CI/CD with your current approach"? I sure am enjoying CI/CD right now. Quite true actually! : htt
32.
by qwer 10y ago
It does, but feature branches become pretty useless at that point. It makes a lot less sense to have a branch for something you plan to merge immediately after the first commit (though my team actually does this just to take advantage of g
33.
by qwer 10y ago
The pomodoro technique makes work easy to start because it's a promise to yourself that it will only be for a limited amount of time. If you break that promise to yourself by not stopping, you've lost the entire point.
34.
by qwer 10y ago
Except your rspec example isn't a change to the underlying language is it? Also, Check out mocha for the JavaScript equivalent. Also, when you use only one function of lodash, you can't call it a language, but there are chains an
35.
by qwer 10y ago
"Made it possible", or "made it look like R"? add() vs. + is just a mild inconvenience IMO compared to the inconvenience of overloading abuse that I normally see ( like sqlalchemy IMO ). I'd personally rather kno
36.
by qwer 10y ago
DSLs are actually common in javascript. JQuery, one of the most popular libraries in all of javascript is mostly a DSL for DOM manipulation. Lodash/underscore is mostly a DSL for list manipulation. Admittedly, JS doesn't have op
37.
by qwer 10y ago
These laundry lists of js warts get dragged out continually, so I really have to ask: How are you people actually developing in javascript and haven't yet discovered linters? Linters have been around for over a decade and solve all of
38.
by qwer 10y ago
All of his arguments actually apply to all of javascript, and are not actually specific to node.js though.
39.
by qwer 11y ago
That's a flaw in how you use node, not node itself. We run dozens of instances of node without internal process state, the need for sticky sessions, etc. You're losing a lot of load-balancing ability by not keeping this discipli
40.
by qwer 11y ago
> You cannot write unit tests for all plausible values sent to your functions. While this is true, static type checks do even less for this problem. Do you even create specific types for value ranges eg IntegerBetweenZeroAnd100? You&#x
41.
by qwer 11y ago
Since I unit-test the heck out of my code, this doesn't really do much for me. Unit-tests test actual values (which is where the interesting bugs come from IMO) and give me more powerful refactoring capabilities than an IDE. The real
42.
Ask HN: Has anyone updated an Android app from free to having in-app purchases?
5 points by qwer 11y ago|1 comments
43.
by qwer 11y ago
> I'm not quite as adverse to long lived branches as some seem to be, especially with CI systems that can automatically detect merge conflicts when they first occur and run automated tests on the merged code base. This system of bra
44.
by qwer 11y ago
> I never understood why some people are scared of branching. Well this is branching (in the same way that if..else is branching), just not in the VCS. What's the advantage? This methodology can allow code to go to production fo
45.
by qwer 11y ago
> How would Seth feel if I make the same amount of money as him just by sitting at home (obviously an extreme scenario from one aspect)? That's the entire point of the article. He's saying your compensation for doing nothing a
46.
by qwer 11y ago
Not only that but by finding themselves a scapegoat, management has ensured that in the future, honest mistakes will go completely unreported. These execs are clearly more interested in CYA than actual results.
47.
by qwer 11y ago
None of your points are actually particularly necessary for agile. For example, I work on a team that does planning on demand (which is still many times per week) and deployments all day long, so we don't do iterations at all. Check
48.
by qwer 11y ago
Retros are my #1 as well. Retros can derive the rest of the changes that need to be made, and if you're doing them right, the team will be making the changes together. My next two are: #2 Never say "Agile" again. If you ca
49.
by qwer 11y ago
So then there really isn't evidence is there?
50.
by qwer 11y ago
And there's not going to be evidence like that any time soon. Software Developer productivity is extremely difficult to measure. It has very little to do with how busy you manage to keep yourself.
51.
by qwer 11y ago
I agree. I've worked on small highly collaborative teams for the last 10 years and any time we're not in the same room, it's annoyingly and obviously less productive. I'm sure that the productivity studies are not taki
52.
by qwer 11y ago
> good communication out of the office is equally as much of a challenge as good communication inside the office Working from home may have a bunch of advantages, but it's pretty tough to believe that it's anywhere near equal i
53.
by qwer 12y ago
That still doesn't explain how the singleton is better / easier. It just explains why it's not that bad.
54.
by qwer 12y ago
My biggest problem is definitely the source maps. It took me forever to get them to "work" and while the stack traces are mostly correct, they're often off by a line number or two. This makes debugging ridiculously hard whe
55.
by qwer 12y ago
Composition in this sense is talking specifically about composition of objects . By definition, that's only going to be possible in languages with objects. No other paradigm achieves that (for better or worse).
56.
by qwer 12y ago
npm already does this from any git repo. I have no idea why anyone would want to tie themselves to github only.
57.
In Defense of the Office(caines.ca)
2 points by qwer 13y ago|0 comments
58.
by qwer 13y ago
"Strong-typing vs weak-typing" is actually irrelevant. It's still an error at run-time, and unless your quality control tools and practices actually run the code (like unit tests do), you're not going to know about them
59.
by qwer 13y ago
I honestly have no idea what's so confusing. I've been working with javascript for over a decade and have NONE of this memorized, and I never look it up or check it in the repl. It's simply not an issue if you're using
60.
by qwer 13y ago
There are javascript implementations that don't go asynchronous though. Take rhino for example: http://stackoverflow.com/questions/7249252/read-file-with-rh... . Or check out the commonjs spec: http:/

More ›