jammycakes

23 ms·

61.
by jammycakes 12y ago
In my experience, if you are to learn Git properly, you need to start off with a GUI. Some of the concepts behind DVCS, such as the DAG, merging, resolving conflicts, even the staging area, are much easier to understand when you can actuall
62.
by jammycakes 12y ago
The main thing I'd recommend here is this: start building up an online portfolio. Get yourself a GitHub account if you haven't already done so and start contributing to one or two open source projects. Submitting pull requests or
63.
by jammycakes 12y ago
My first reaction on reading this was, "What about the Unsolicited Goods and Services Act and similar legislation?" However, a few minutes of Googling and reading up on contract law on Wikipedia suggests to me that there's a
64.
by jammycakes 12y ago
Yes, but if you're doing curl ... | sh then you're not vetting the script you're running before you run it. If you were, you'd be running curl and sh as separate commands.
65.
by jammycakes 12y ago
Having been in a similar situation myself, it's obvious to me that you're working for a company that's circling the drain. Low employee retention is toxic even when management is actively recruiting to fill the gaps that are
66.
by jammycakes 12y ago
> I do not think you can generate enough great code in a few days to get noticed. I'd agree that you can not generate enough great code in a few days to get noticed by the open source community in general . However, you can gen
67.
by jammycakes 12y ago
> As a former manager who has hired dozens of programmers, I think that's stupid, because it vastly limits your pool of candidates to people who have time to contribute to open source. I've found that there are lots of very gif
68.
by jammycakes 12y ago
> I would also say you'll probably be using SVN and not git. According to http://www.itjobswatch.co.uk/jobs/uk/php.do these are the number of PHP jobs asking for Git and Subversion respectively in the UK i
69.
by jammycakes 12y ago
The fact of the matter is that love it or hate it, Git is now the most widely used VCS on the market in corporate settings (see e.g. http://www.itjobswatch.co.uk/ ). More importantly though, it is also the de facto standard
70.
by jammycakes 12y ago
Actually, reCaptcha requires a specific word to be correct. Specifically, the illegible one. The article does make this point.
71.
Eclipse Community Survey 2014 Results(ianskerrett.wordpress.com)
3 points by jammycakes 12y ago|1 comments
72.
by jammycakes 12y ago
The main utility that I see in the OWASP Top 10 is as a baseline for the knowledge that we should all be expected to have as developers about web security -- knowledge that should be tested at interview, for instance. My main criticism on t
73.
by jammycakes 12y ago
The one thing I don't like about GitHub for Windows (and GitHub in general) is its lack of a graphical view of your branches. I've found that a DAG view is indispensible for understanding the mechanics of branching and merging, an
74.
by jammycakes 12y ago
You can get some interesting usage statistics from job tracking websites such as itjobswatch.co.uk. In the source control market, Git is now the most widely used (3461 jobs) with Subversion second (3181) and TFS third (2035). Mercurial is a
75.
by jammycakes 12y ago
My problem isn't with this article specifically. In fact I'll probably find it quite useful myself: it's one of the clearest presentations of Git's internals that I've seen so far. I personally have no problem with
76.
by jammycakes 12y ago
Yes, but if you choose to use a CLI for your explanation, you are alienating an even larger portion of your readerbase who can't use/don't want to use the command line. I'm thinking in particular of Windows developers, w
77.
by jammycakes 12y ago
The thought has occurred to me. Just never got round to it, that's all...
78.
by jammycakes 12y ago
Atlassian SourceTree mainly. Git Extensions is also good if you need Visual Studio integration, though personally I find it visually a bit harsh.
79.
by jammycakes 12y ago
What disappoints me most about this, as well as almost every other Git tutorial that I've seen, is that it uses the command line almost exclusively. Even those tutorials that I've seen that do refer to GUI options pay lip service
80.
by jammycakes 12y ago
No, defaults are important. It's the difference between "doing the right thing by default" and "doing the wrong thing by default." Unicode may be of little relevance to some disciplines, such as scientific computing
81.
by jammycakes 12y ago
Nobody should be sticking to plain ascii/latin-1, and certainly not inexperienced developers. The only valid reason for using anything other than UTF-8 these days is that you are interacting with a legacy system that doesn't sup
82.
by jammycakes 12y ago
Yes, but it's not the default and it does require special considerations. This means that code written by inexperienced developers (or even more experienced developers who aren't familiar with the ins and outs of Unicode and inter
83.
by jammycakes 12y ago
I've never really understood these claims that Python 3 only offers minor improvements over Python 2. Some of the improvements in Python 3 are quite significant: the example that comes to my mind first and foremost is that strings are
84.
by jammycakes 13y ago
Probably. It's one of those things you learn as a Git user sooner or later -- though in most cases, not before a few heart-stopping moments and probably a bit of an injection of FUD into your team. Rather more worrying is the possibili
85.
by jammycakes 13y ago
I'd just like to respond to all the people who are saying "Use the reflog" here. Yes, you can recover lost commits using the reflog. But it is not well publicised that you can do this. Most tutorials do not mention it and mos
86.
by jammycakes 14y ago
In that case it's probably sensible to break it up not only into separate projects but separate solutions too. What bugs me is when relatively small solutions are broken up into large numbers of projects. Very often it's done for no reason
87.
by jammycakes 14y ago
When I look at the Ruby/Rails community, the word that comes to my mind more than any other is hubris . You see this in things such as security issues being marked as wontfix until they are actively exploited (e.g. the Homakov/GitHub incid
88.
by jammycakes 14y ago
Yes but that's not the case if you're changing a dependency in the middle of the chain, as is more commonly the case. Additionally, as far as I can tell, the main thing that slows compilation down isn't so much the actual compilation step a
89.
by jammycakes 14y ago
The problem is that large swathes of the Git community have been treating the whole DVCS scene almost in Hunger Games terms -- there can be only one winner, and all the others must die. For what it's worth, I've heard quite a lot of anecdot
90.
by jammycakes 14y ago
It's sadly far too common for .NET developers to carve up their solutions into far more projects than are necessary. This can seriously slow down compilation times.

More ›