Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nahname
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
49 ms
·
451.
▲
by
nahname
15y ago
If you are writing tests and can switch from iteration to recursion without tests failing, you are missing the point. Code quality is derived primarily through unit tests. Refactoring relies more on integration tests. Refactoring SHOULD bre
452.
▲
by
nahname
15y ago
I think poor IDE support is pretty unilateral because git is supposed to used from a command line. It is great to work with a tool where the UI is an after thought because the UI will always be cumbersome with something as complex as source
453.
▲
by
nahname
15y ago
"People that work at SAP are just like people working in startups or anywhere else." { sarcasm: "Yes, a company that spends more on marketing and 'bribes' is just like a start up and the people that work there are too." }
454.
▲
by
nahname
15y ago
The best code is the code you don't need to write. Build only what you need (YAGNI) and introduce abstraction to avoid duplication (DRY). My rule is don't ever do the same thing three times (though I sometimes enforce it at two). Conversely
455.
▲
by
nahname
15y ago
I am glad the comment (heh) helped you in some way.
456.
▲
by
nahname
15y ago
I've spent quite a bit of time working on systems that became untenable and had to be partially re-written or completely re-written. The result is the original code was either a baseline or a reference. I will say, without a doubt, comments
457.
▲
by
nahname
15y ago
I'm curious, are you against unit testing in some scenarios or just TDD? I'm sure we can think up some conditions where the cost won't be returned. Is that all you mean?
458.
▲
by
nahname
15y ago
And that right there is why they are generally a bad idea. You can write a condition to check how to save your data or you can write the code necessary to verify a user's email address. Assuming you have time for one task, which is more val
459.
▲
by
nahname
15y ago
What is your background, if you don't mind me asking.
460.
▲
by
nahname
15y ago
Not just that, I believe he didn't commit anything and was using git pull to update his workspace.
461.
▲
by
nahname
15y ago
The biggest issue here is not committing before pulling. Always commit all of your changes before updating your history (either through git pull, git fetch/merge or git pull --rebase).
462.
▲
by
nahname
15y ago
When calling fetch and then merge (or using rebase), you have more control over how the other changes impact your commits. Just pulling will result in a merge commit that contains all of the changes between the point you last pulled. This b
463.
▲
by
nahname
15y ago
It is really disruptive having to explain something from "muscle memory" in logical terms. That said, a good programmer should always be able to explain what they are doing to another capable peer. Years of experience as a quality gauge is
464.
▲
by
nahname
15y ago
It is if you don't want to write side effect riddled 'objects'.
465.
▲
by
nahname
15y ago
HBO has always included a substantial amount of nudity and sex in many of their shows (Rome comes to mind as one of biggest offenders/supporters). Unsurprisingly, sex and violence sells. I am not wholly against this, as there are scenes in
466.
▲
by
nahname
15y ago
The show is really for people who have read the books. It is accurate to the first novel and even contains a significant amount of dialog from it, but it doesn't frame things as well as George Martin's writing can. I especially noticed this
467.
▲
by
nahname
15y ago
The google+ iphone app is very well done. I have heard third hand that google spends a lot of time writing low level interaction code (re-writing swipe gestures to be 20% faster, etc...) solely for cocoa. I am not sure of the truth of that,
468.
▲
by
nahname
15y ago
I am just one data point, but I used to be a hardcore console guy and now mostly play games on my phone + ipad. There are more interesting things happening via touch and/or mobile than what I am finding in console games. My home theater sys
469.
▲
by
nahname
15y ago
If you don't work in the code you shouldn't get an opinion and giving one to someone like that is asking for trouble. At the end of the day, it will be a developer who feels the pain, not the architect. There really is no incentive to do a
470.
▲
by
nahname
15y ago
Sign...what a lovely tech stack you have there.
471.
▲
by
nahname
15y ago
What is it about the syntax that you dislike? I am neither for or against, I just have friends that use it quite frequently and seem fine with it.
472.
▲
by
nahname
16y ago
What do you mean by "type of programming"?
473.
▲
by
nahname
16y ago
He really does not come off well in those comments. Repeatedly saying I am successful, therefore what I am doing is right. In his defense, it sounds like he has mostly worked by himself. Some practices don't have a very good ROI when you ar