gustavo_duarte
Joined 18 years ago
Joined 18 years ago
As a counter, my intuition is that masks also remind people of the risks and actually encourage safe behavior. I feel this in myself, a greater awareness of the pandemic, a nudge towards being more careful. Extending your analogy, it's as if the seatbelt reminded people that there are some pretty grisly accidents out there, and maybe they should take it easy.
Both effects probably exist, not sure what wins out, and how much it matters.
Your code remains living in its original repo. To keep things easy, it'll support only GitHub repos at first, then any Git repo, then potentially other source control software.
"The word "hacker" in its well-known computing sense has a first citation of 1971 (contributed by me) in the Historical Dictionary of American Slang. Here is an earlier citation, not precisely in a computing context but obviously the same term"
I interpret that as the only condition on the citation being "the well-known computing sense." He's definitely not saying "with negative connotations."
Even the phreaking stuff from the Tech is "not precisely in a computing context". I don't think the TMRC citation qualifies here, it's a very specific and different context (check some of its sibling entries), even if it shares some of that early magical MIT spirit.
But even then, the TMRC does also say:
"HACK: 1) something done without constructive end"
So, all in all, even taking the TMRC into account I think the origin of the word was already ambiguous, which it is. I think the small dash of mischievousness adds to the flavor of hacking.
The “sources of material” included many people the
Nazis sentenced to death for minor crimes, such as
looting, and many convicted for political crimes that
particularly incensed the regime, ranging from treason to
the vague offense of “defeatism.”
As an example of this, Elfriede Scholz was sentenced to death for “undermining morale” in 1943 for saying she thought the war was lost.However, I think the main point of the article still holds and is important in our fight towards a stronger rule of law.
There's a political game being played here, and we need to see it clearly. I don't mean to defend Obama at all, but _any_ administration is under extreme pressure to "fight terrorism" and this creates a huge distortion between the actual risks and consequences of an attack compared to the measures taken by the Executive branch to: 1) avoid attacks, and 2) create the perception they're doing all they can to avoid attacks. There are also other players, like the defense industry, federal departments, etc., with their own interests at play.
Remember DFW's commencement speech? [0] In our situation the political game _is_ the water. We need to see it clearly to fight back and keep our societies lawful and free. While logic is important, it's not going to win an essentially political battle.
0: http://moreintelligentlife.com/story/david-foster-wallace-in...
http://www.economist.com/blogs/democracyinamerica/2013/06/wh...
Think about the incentives to the _President_ (whoever that is) to NOT let an attack happen, no matter what the cost. As Daniel says, it's not about numerical risk or objective damage, it's perception. Obama would have done anything not to have an attack during his terms.
And that's the really sad part. Due to the political process, different interests, and so on, the terrorists WERE able to inflict grievous damage to us as a society.
I use GH for about 12 hours a day almost every day, between open source and client projects. I face slow downs in the issue tracker, the git repos themselves (I only use command line), and the web interface to browse a project (code, history, pull requests). I notice a slow down about once a day. Some features, like the contributors graph, are always dead slow. About 10-20% of PR merge attempts fail, and I have to click the button again, sometimes multiple times. I see the Unicorn fail page or some Octocat fail page often enough.
It makes me think exactly of what you describe, a combination of Rails perf / scalability and perhaps a lack of strong backend engineering, I'm not sure.
Right now the problems are in the level of a mild annoyance / surprise that a company like GH has these issues. If it gets worse, I would consider moving away. But because I truly love the UI and overall functionality, it's a positive tradeoff for us at the moment.
You're very welcome regarding the YouTrack suggestion.
The UI and milestones, though, I think are good. JIRA is to me the king of clunky. I've used it in 3 projects over the years and evaluated it last year, and I've been pretty disappointed with it.
To borrow from another comment here, it has a bit of a Bugzilla feel, like it just grew and grew, and you have tons of fields and features, but they're poorly designed and put together. A bit of a mess, to put it bluntly. FogBugz has a similar feel to me.
I encourage you to check out JetBrains' YouTrack. I never used it in a project, but a couple days evaluating gave me a good impression. Good luck with your search.
After toying with different solutions, we settled on using two dedicated issues-only repositories. One of them handles software development (all bugs, feature requests, the engineering stuff) and the other handles operational stuff like client installs and so on.
This has worked well for us. Here are some advantages:
0. We get the big picture you mentioned, which is the crucial point. Planning, grouping issues for releases, etc., becomes much easier.
1. When it comes to access security, we can give people access to the issues repositories (via GH teams) without giving them access to the full source code.
2. Splitting operations and engineering increases focus. Engineers don't need to look at client installs, etc.
3. We can still reference repo issues in commits to other repositories. See [0] and [1]
So all in all, I agree the fragmentation is a real problem, and I think centralized issues-only repos are the way to go. Hope this helps.
0: https://github.com/blog/1439-closing-issues-across-repositor...
Have you used the GitHub mobile apps though? I find it's a decent way to keep tabs on issues, add comments, etc., when one is away from a bigger computer. I see that as a big plus for GH.
If you're interested in a HN meetup in Colorado, drop me a line.