rockhymas

6 ms·

1.
by rockhymas 26d ago
Abstraction is compression, and abstraction is definitely a core component of intelligence.
2.
Cue: Hello, World(cueplan.com)
2 points by rockhymas 1mo ago|0 comments
3.
A Professional’s Home Office: 6 Keys to the Castle(rockhymas.com)
2 points by rockhymas 10y ago|0 comments
4.
More cool stuff in Kiln Harmony(blog.fogcreek.com)
1 points by rockhymas 14y ago|0 comments
5.
by rockhymas 14y ago
Kiln Harmony won't save as much money and angst as a DVCS that automatically converts tabs to spaces and back, based on personal settings, or one that changes bracket code formatting, but it's a start.
6.
by rockhymas 14y ago
This makes it easier to bring on new team members who are more familiar with or comfortable with one DVCS. And the (admittedly slight) gains in productivity for some of your developers is a nice bonus.
7.
Learning coding from boredom(bitquabit.com)
5 points by rockhymas 15y ago|1 comments
8.
by rockhymas 15y ago
New York City -- Full Time Software Developer Fog Creek Software is hiring full time developers, sales positions, and we're open to looking at intern resume's for summer 2012. http://www.fogcreek.com/careers.html
9.
by rockhymas 15y ago
I would agree. Though C is far from useless, it really isn't used here at the Creek. Which was a double bonus for me, since after 6 years immersed in C and C++ I could find a job that let me do something new but that I felt very comfortable
10.
Drowning in a C of Interviews(blog.bitquabit.com)
54 points by rockhymas 15y ago|23 comments
11.
Startup Exercise: What can’t be solved with money?(blog.asmartbear.com)
41 points by rockhymas 16y ago|2 comments
12.
Have a mission, not a mission statement(blog.bitquabit.com)
16 points by rockhymas 16y ago|2 comments
13.
When Things Go Well - Weekend Deployments Followup(blog.bitquabit.com)
5 points by rockhymas 16y ago|0 comments
14.
Weekend deployments are for chumps(blog.bitquabit.com)
93 points by rockhymas 16y ago|41 comments
15.
Deploying FogBugz 8 and Kiln 2(thoughts.rockhymas.com)
21 points by rockhymas 16y ago|11 comments
16.
Do not store the output of a build in your VCS alongside your code(thoughts.rockhymas.com)
3 points by rockhymas 16y ago|0 comments
17.
Build script parameters(thoughts.rockhymas.com)
1 points by rockhymas 16y ago|0 comments
18.
Keep build and deployment scripts separate(thoughts.rockhymas.com)
1 points by rockhymas 16y ago|0 comments
19.
Don't let your build scripts get crusty and old(thoughts.rockhymas.com)
1 points by rockhymas 16y ago|0 comments
20.
Deploy your product with one command(thoughts.rockhymas.com)
2 points by rockhymas 16y ago|0 comments
21.
Dev Machine Setup Scripts(thoughts.rockhymas.com)
1 points by rockhymas 16y ago|0 comments
22.
Keep your build scripts and deployment scripts separate(thoughts.rockhymas.com)
1 points by rockhymas 16y ago|1 comments
23.
Hard dependencies in your build scripts(thoughts.rockhymas.com)
1 points by rockhymas 16y ago|0 comments
24.
by rockhymas 16y ago
You're totally right on the path to the source code. The build scripts, as typically run by a developer, should actually do two things: 1) build the code into binaries and 2) deploy those binaries on the developers machine so he/she can eas
25.
How to eliminate absolute paths from code and build scripts(thoughts.rockhymas.com)
2 points by rockhymas 16y ago|0 comments
26.
Where you should keep your checked-out source code(thoughts.rockhymas.com)
2 points by rockhymas 16y ago|3 comments
27.
Can you build your product with one command?(thoughts.rockhymas.com)
2 points by rockhymas 16y ago|0 comments
28.
What is build and release management?(thoughts.rockhymas.com)
2 points by rockhymas 16y ago|0 comments
29.
Mercurial will make you a better developer(rock.hymasfamily.org)
1 points by rockhymas 17y ago|0 comments