HN user

daven11

45 karma
Posts6
Comments48
View on HN

Yes I've often maintained that we could just drill a hole in the middle of Australia and dump the worlds nuclear waste in it. Its the perfect spot, no ground water (if you make sure its west of the great artesian basin), geologically and politically stable, no one lives there for miles, and there's already a shit ton of radiation there anyway - thats where the Uranium comes from.

One problem would be transporting it, but again, solvable problems, we tanker oil around the world, so it can be done. The trouble is though political. No one wants all that nuclear waste in their back yard, even if no one ever uses the backyard.

Fukishima added to the problem - if the Japanese, whose engineering skill is the best in the world, have problems then what about the rest of the world? I see this as a very valid objection.

One of the problems I see in the popular mind is the idea that radiation is somehow unique and only occurs in nuclear reactors, and any of it appears somewhere then we're all dead. The coal industry makes sure no one finds out that the amount of radiation expelled by coal powered stations exceeds that produced by nuclear reactors https://www.scientificamerican.com/article/coal-ash-is-more-...

As you say the amount to be stored is pretty small, and could probably be dumped down a hole in an afternoon and home in time for tea

An anecdote - I went to a radiology clinic a while ago for a tour (writing some software) and we stopped by the room where they store the radioactive material, pretty low level stuff and all stored away. The manager taking me around said "This is where we store the radiocative stuff" looking at me and waiting for a reaction - a bit of fun I imagine he has - expecting me to run away and panic, but I have a physics degree so no drama - he was disappointed, and we laughed. But this is the public mind - radiation is scary stuff that causes mutations and kills you, so there's a real marketing problem. No doubt this has been pumped up by the oil and coal industry over the years.

oh, I just had a look and the base model doesn't have an SSD - I'd really not consider developing without an SSD any more. It will work but compile times are slower, how much I couldn't say. But then I've developed for years without an SSD before that so...

( the reply link appears after a few minutes)

I use a macbook air mid 2011. 1.7 Ghz i5, 4GB 133MHz DDR3, 128GB SSD, intel HD graphics 3000 384 MB memory, and it works fine. I run Yosemite on it and develop iOS apps. I actually run a Windows 8 VM on it as well - but I have to be careful with the memory usage :-). I keep looking for an excuse to upgrade it but I have no reason :-(

If you buy from Apple you can return it in 14 days no questions asked - at least in Australia last time I looked. I tried this once with an external hard drive (too noisy) and it was not a problem.

I was self taught then did a CS degree, so have a foot in both camps. Some of the things I learnt in the degree which I never would have learnt by myself were (and others have mentioned some of these) - algorithms, relational theory, O-notation, symbolic logic, stats, CSP. Then there were things I learnt myself that I never learnt at uni because I wanted to - assembler, 2d/3d graphics, c++. Then there are things I've taught myself since uni - compiler theory, database optimisation, functional programming (actually did this at Uni but couldn't see the point then - hardware was rubbish then though), web stuff.

So difference would be in broad for my case - uni gives you the theoretical foundations that you probably wouldn't learn yourself, teaching yourself programming gives you the hands on stuff you'd never learn in depth at a uni. Two sides of the same coin I suppose, it would be rare to have a self taught person learn the theory that you'd learn at uni, and I don't think you'd ever get that depth without some uni training imho.

The other thing that comes to mind is if you're smart and self taught - why wouldn't you do a degree? The only good answer I can think of is that you're so friggin awesome you're churning out code that everyone says is awesome and google or apple has hired you already, there are perhaps 10 people in the world like this - everyone else do your degree :-)

Managers who hire specialists in a field (i.e. me) then proceed to tell them how to work. It's solvable, but the cost is me taking on the risk of ignoring managers and proceeding, or present the reasons why their approach will fail and wait.

until someone comes up with a way to determine what is bad versus good then that is perhaps the best there is. I use companies to do all sorts of things for me - watching software is just one more thing.

...or come up with a better way to download and install software, oh wait a minute Apple did that and made a billion dollar industry downloading apps.

For those who don't live in Brisbane. The brisbane times is a free paper put in peoples letter boxes, best known for it's local restaurant reviews and fashion. I wouldn't take it's views on overseas IT procurement very seriously :-)

If you want to do web browser then javascript

For apple (IOS/OSX) then objective C or maybe Ruby or lua

Embedded programming then C

Microsoft you have a large choice C# or VB.Net perhaps

Android is Java

Enterprise programming then Java or C#

Pose value haskell or scala :-)

It depends on your background and what you want to do. I think every developer should know C or C++ but not as a starter unless you like serious hacking. Javascript is the language of the web browser so you'd need to know that for any browser programming. Enterprises run on C# or Java.

Then of course there are all the scripting languages python is perhaps the most popular for general scripting, or powershell for windows

I use a very simple version of function point analysis. Write down all the different things you know you need to do, beside each one write easy, medium or hard. easy takes 0.5 to 1 day, medium 2-3 days, hard 3-5 days. If you think any bits are very hard then break it down - if you can't then you've found something you don't know - and you have to focus on that - this is a risk and flag it as such.

If it's a big project then chop it up into deliverables, so you can monitor your estimates along the way.

..there's a lot more but something to get you started.

(if you have to deliver on your estimate - double it :-). When you double your estimate - make sure you don't work to your doubled estimates - otherwise you'll have to double it again :-) )