lukeck

I didn't have a very high opinion of Jira until about version 4. In recent updates, a lot of the clunkiness of older versions seems to have been cleaned up.

Until recently, my team was the only developer group in our company using an issue tracker. Management have decided that every team must now use an issue tracker and that tracker must be HP Quality Center. They're even paying a temp to manually migrate all our Jira issues into QC. We managed to win the battle for Git over IBM Rational ClearCase for a version control system but this kind of thing makes me think it's about time to find a new job.

Jira.

In what way does using HTML5 over plugins decrease the potential for competition? If anything it makes for more competition as the need for browser-specific plugins is removed.

Specifically where were you getting stuck with Ruby/Rails? My background is C#/ASP.NET MVC too. The structure of a rails app is not all that different to that of an ASP.NET MVC app. The biggest challenge for me was adjusting to all the extra syntactic sugar in Ruby compared to C#.

Michael Hartl's Rails Tutorial was what I used when picking up Rails. http://ruby.railstutorial.org/

railsguides.com has some pretty great videos on using different rails libraries.

If you're really not a fan of the Ruby syntax, maybe something like Python with Django would suit you better.

If it's missing the Visual Studio IDE that's giving you trouble you might want to check out the RubyMine IDE (made by the same devs as the Resharper VS add-on).

Have a look at MIT Open Courseware.

Cool. It does seem like a good base to build upon. Good luck.

I like the way you've implemented this but what practical advantages does it have over adding the line

alias zack=ack -i --ignore-dir node_modules --nojs

to your .bashrc (or .zshrc or whatever) file?

Interesting. I'd love a link to a board that has either or both Sara or gigabit eth if someone has one handy.

Think about the next small thing you can do right now to move it forward from being just an idea. Do it. Repeat.

I have terrible eyesight (somewhere between legally blind and failing a drivers' license vision test) and I find my eyes are usually less tired at the end of a day working on my retina MacBook than they were after a day of using my old 1440x900 13" laptop.

Smaller text is more legible, and larger text is less jagged around the edges so both seem to be less of a strain on my eyes. My thinking is that the sharper the image displayed, the less work my eyes and brain have to do to fill in the gaps.

This could all just be me subconsciously trying to justify the purchase (although I have no regrets about it) and obviously YMMV so I'd suggest going into a store and doing a side-by-side comparison using an application that has been updated for the retina resolutions.

I'm happy to see relevant promos here as well because I would miss out on them otherwise, but it's a slippery slope.

Perhaps we could have a convention for post titles or a separate section for them?

Apologies if this idea has been floated and rejected before.

I could have been clearer in my original post. Let me clarify by addressing your points. 

1. People get into planes and cars every day routinely because we have been using these technologies for decades. Any new technology that comes along will be held to much higher expectations of safety and quality than currently available modes of transport were at their inception. Understanding the risks and learning how to mitigate them to an acceptable level will take some time but we should be able to get some of the benefits of high speed transport earlier.

2. I'm not suggesting making an unsafe for humans version or a version with incompatible design goals. At some point on the path towards having a system that is acceptably safe for humans, there must be a system that is safe enough to send non-human cargo so why not take advantage of that? Having a real functional system would allow larger scale testing that could provide very useful feedback when trying to work out all the kinks before human passengers get on board.

3. Good point. I've got no idea of the scale of any impact on road usage that this would have. It may or may not be a compelling goal by itself, but as a side effect of implementing technology that is a necessary stepping stone to transporting people, it could at least be a nice bonus. Negative PR from job losses comes along with many disruptive technologies and is generally an area where there's lots of room for improvement.

Shipping may be invisible to most but people do notice the ease of access to goods, in their availability and price. The eventual possibility of cheaper same-day shipping over large distances sounds okay to me. This doesn't have the same direct impact to an individual as being able to travel that far or fast themselves but its a start. I might be going out on a limb here but it seems to me that having faster means of moving goods around at large scale should make much more efficient distribution of resources possible. That's something we can all benefit from.

I'd be disappointed if Elon did shy away from the goal of a new form of human transportation but no one has said that's what SpaceX are doing when they send unmanned capsules up to the ISS.

Replacing a rail freight line with a system that can potentially move physical goods at the scale of road freight at twice the speed of air freight, and doing it cheaply, could be Hyperloop's minimum viable product.

I haven't had to deal with any support issues with them yet but, for the sake of a couple of bucks, it's worth it to me to avoid the constant up-selling and misleading sales tactics employed by some of the other registrars.

OLinuXino (Multiple models: IMX \233 Maxi, Micro, Mini, MiniWiFi, A13, A13WiFi) https://www.olimex.com/Products/OLinuXino/

MK808 (Updated MK802)

The RaspberryPi Model B has been upgraded to 512mb RAM.

Several other devices mentioned in http://www.reddit.com/r/linux_devices

Very cool idea. I've been discussing different ways race data could be visualized with a friend as we watch the race, checked HN during a commercial break and found this. Thanks.

This series of posts has been really interesting. At first I was dismissive and found myself disagreeing with a lot of the assessments but the explanations of why one language's approach is better from a beginner's perspective can tell us much about better ways to teach programming.

What sort of timeframes did it typically take for these sites to become profitable? Are there any trends you've noticed or other details you wouldn't mind sharing?

I'm not sure where it sits on the scale but the internet, web and associated technologies allow anyone to share without the limitations of physical media, an idea with any other person across any distance from across the room to as far as people spread in future and across time from instantly through to the end of civilization.

I'd say that's a fairly fundamental change for humanity.

What do they hate about it? I'm trying to "walk a mile in their shoes" as another poster put it but am coming up blank.

Was P. shorthand for PRINT .? No idea what the other two commands do I think *OPT was for addressing a serial port or the screen but my memory is very hazy.

BBC BASIC on the original RISC PC was my first experience writing code. I think that machine is still in my parents' garage along with the 6 volume BBC BASIC reference manual.

Very few, if any people can keep every detail of a system as complex as a modern piece of software in their head at once. As developers we just have to accept that. Understanding the big picture, and how all the parts of a picture fit together is still important so rather than trying to load everything into our brains at once, we can focus on a part at a time and develop a good test suite that will point out the effects of any changes so you don't have to try to anticipate them and can focus your energy on he problem at hand.

Expanding on that, having a good set of automated tests gives you confidence that all the pieces of the system fit together properly. With good tests in place, you can focus on changing a small part of the code without having to understand how it relates to every other part of the project. If the small change affects anywhere else you'll see this in failing tests.

If you aren't already, start writing unit and integration tests for your code. It can feel like unnecessary overhead at first but you quickly reach a liberating point where you can lean on the tests to tell you how any changes affect the bigger picture.