Ramone

7 ms·

1.
Return of the Spec: Why AI agents are reviving the software specification(caines.ca)
1 points by Ramone 1mo ago|0 comments
2.
How you do QA is probably terrible(caines.ca)
2 points by Ramone 6y ago|1 comments
3.
by Ramone 12y ago
I droned on and on about it in a blog post once if you're interested: http://caines.ca/blog/programming/in-defense-of-the-office/ . In my experience, it's waaaay more efficient for developers to be
4.
by Ramone 13y ago
We do this too, attaching req and res objects to a domain, as well as databases and other network related objects (like smtp clients, etc). This is a huge improvement, but I'm still seeing occasional uncaught error events in our logs
5.
by Ramone 13y ago
I actually think I understood you, but I'm saying that in that case where statelessness should be an advantage, node.js is actually a much less fault tolerant environment when you compare it to most other web application servers. Most
6.
by Ramone 13y ago
It's actually pretty silly to write node.js apps in a crash-only manner. Since they often handle thousands of connections concurrently, a failure in one client's processing is pretty horrendous if it brings down a whole server (e
7.
by Ramone 13y ago
I know you feel like you just explained its flaws, but there's nothing here that couldn't also be said about any other mainstream language.
8.
by Ramone 13y ago
I consider that to be a bright spot in this post. What would a performance comparison for this very specific app prove? The way I read it, the only goal of the rewrite was a more easily maintainable code-base with performance that was "go
9.
by Ramone 13y ago
That's actually a solved problem (in node.js at least). npm builds a node_modules tree where each package gets its own copies (with the correct versions) of its dependents. Gone are the days when people took on dependency hell for a few
10.
by Ramone 14y ago
There are a benefits, but most people won't notice them without first actually using a hypermedia API. * It's self-documenting. Client developers can find all the endpoints just by clicking around (instead of reading mountains of docs). *
11.
by Ramone 14y ago
GET being cacheable/idempotent is part of the HTTP spec, and has nothing to do with REST: http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13...
12.
HyperJSON(caines.ca)
4 points by Ramone 14y ago|0 comments
13.
by Ramone 14y ago
Looks more like JS the java way. Singletons make no sense in a language that has global variables and never lets you stop an object from being duplicated. The command pattern makes no sense in a language with first-class functions. I'd s
14.
by Ramone 14y ago
Well every team is different, so I shouldn't try to say I know the right thing for your team. What you're talking about though is farming out your branch builds/tests/deploys to jenkins, which has nothing to do with CI, but still sounds li
15.
by Ramone 14y ago
I'm saying a CI server is unnecessary for these branches that aren't ready to integrate with master. These are short-lived branches with 1 or 2 contributors, right? Just run the build/tests locally. There's no advantage to this overhead
16.
by Ramone 14y ago
It sounds like we agree that long-lived branches are not continuous integration at least. We probably differ in that I think short-lived branches and pull requests are more overhead than most teams require. Keep in mind that CI does expec
17.
by Ramone 14y ago
But then it's not really continuous integration anymore is it? Having a CI server and practicing continuous integration are not the same thing.
18.
by Ramone 14y ago
The normal usage of the term "Lean" (ie from Toyota) actually has little to do with validated learning and more to do with the elimination of wasteful aspects of production that don't directly lead to customer value. Usually that means "pu
19.
by Ramone 14y ago
I think the argument that we shouldn't rely on the parser for certain language features is a bit silly (including interpreting end-of-statements). The language is precisely what the parser says it is, and nothing more or less. JSMin is f
20.
The Sun is Setting on Rails-Style MVC Frameworks(caines.ca)
13 points by Ramone 15y ago|1 comments
21.
by Ramone 15y ago
I think calling it "superficial beauty" undermines the quality he's looking for, which in my opinion is "human readability". A human has to make multiple passes to parse something like this, and that's entirely unnecessary.
22.
by Ramone 15y ago
It's really all about factoring. You'll notice now that you have model logic in your controller. If you want to reuse that elsewhere, you'll first have to extract it to another class. That class is effectively a SQL generation library, e
23.
by Ramone 15y ago
Figure out how to log only what you want. Don't let your choice of an inflexible logging system affect your external API. What do you get? Well many things, but specific to your inquiries: using GET tells the client of your API that the r
24.
by Ramone 15y ago
You're light on actual counter-examples and heavy on words like "shills", "hocus", "criminal", and "idiocy", so that most of your argument has to rely on your ability to paint TDDers as stupid or evil. The vast majority of thinking people
25.
Agile, the Good Parts(caines.ca)
5 points by Ramone 15y ago|0 comments
26.
by Ramone 16y ago
Conversely, some might say that input from the user and output to the user are really the only important i/o.
27.
by Ramone 16y ago
Smart people are involved. What more do you need to know?
28.
by Ramone 16y ago
It's hard to buy the competitive advantage argument. Why open source it if that's the case? I think they must realize it's not a core part of their business.
29.
by Ramone 16y ago
I'll never understand how people can equate type correctness with value correctness, regardless of the language.
30.
by Ramone 16y ago
Well... God chose Ultraedit: http://www.ultraedit.com/company/IDM_full_story.html ;)

More ›