Bashing people for not using Linux is like bashing people for living in apartments

First off, let's start with everything that's great about houses and linux;
There's a lot of freedom. A LOT of freedom. You can remodel and build whatever you want in it. Want a second kitchen? BAM! Just build one and you got one! You can hire any contractor you want for whatever job you want, you're not restricted by your landlord. You can be as noisy as you want, you're not dependent on anyone else but yourself. There are no secret processes going on that you aren't aware of unless you chose to stay ignorant. Most people who know what they're doing would probably prefer to live in a house.

Hardware limitations transfer to your property's limitations; there may be restrictions about adding little huts or building out your house, but within the limitations, you can do whatever you want, and that is a lot more than when you live in an apartment.

Sometimes it can even be a lot cheaper to live in a house than in an apartment. But if you have to build a house, learning Linux takes time, and time is money. Ubuntu is like a module house or a suburban terrace.house. It's a little bit easier to live in and maintain, but it's still a house. You don't spend as much time building it. But you also loose a little of your freedom. Not to mention, nobody is going to fix things for you. There's no landlord to call about that dripping tap or the hole in your roof. You are your own boss here for the better and worse.

Apartments, like windows and macOS are easily available; they often come with your device, just like apartments are a natural part of a city, whereas houses usually are a bit away from the city core or any city for that matter. There are a lot more options where software translates to stores and services; the demand is higher and therefor the supply. They're cheap, you don't build anything really. With the landlord's permission you may be able to remodel your kitchen, but why would you? When the time comes, the landlord will do that for you. Things run smoothly, but you don't have that freedom you would have in your own house.

For some people, getting a house or a Linux computer is equally hard; there may not be houses where they need to live and if you don't have anyone to help you learning Linux, some might not be able to learn it at all.

For the mass who want the conveniences that a city gives you, an apartment is the best choice. And it only makes sense that an architect or property owner knows how the apartments work in order to develop them. Even if you live in a house, you'll probably still at least have an office in the city.

Sure, houses do have their own services too; you'll find a local store that has the essentials, but it's far from all the luxury you would have wanted. If enough people buy houses in your area, then of course the supply of services becomes greater too, but eventually, they'll tear down the houses and build apartments there too as it becomes a city rather than a village.

Linux is not bad, I love Linux, but it just doesn't make any sense to me to bash people just for using a certain OS. When you know your shit, Linux is awesome! But if you don't know your shit, if you can't build whatever you need when there's no supply of it, you're kinda doomed.

I do agree however that every developer should try to have at least one Linux machine, or a dual boot. Just like I do kind of believe that every developer should own a device running the OS they are developing. Unix is great to learn! But not everyone is capable of building their own house from the very basics.

Relationship blogging

private class SignificantOther implements Adorable {
        private void adorable(IceCream nom){
            nomNom(nom);
        } 
}

private class Me implements Weak{
        public IceCream give(){
            IceCream nom = Cupboard.get("IceCream");
            return Nom;
       }
}

Working hard or hardly working?

Well, I'd say I've been working hard lately. I've learned so much and things are becoming increasingly fun. Not to mention that I just started shallowly network for a job, and it's been way over my expectations result wise. I've been to two interviews for one company and I met one guy who wants to help me network with his contacts. And all this without showing a single line of code. We've talked code though, a lot of code. I love talking about code, but not as much as actually coding. And that is why I want to start working!

Also, the idea of having a job brings me one step closer to having the money to get me my optimization coding machine 3000:

Yes, it's a big thermos. 2,5L should be enough until about lunch.

Working hard

How I feel working on this project:

But hey, I made a log in window so I've got that thing going for me which is nice...

Testing the limits!

Yesterday I spent 13h sending a nice message to as many of my facebook friends as I could fit into that time-frame. I made a lot of people happy, which made me happy.

I feel the exact opposite right now.

I'm suffering from a really, really low self-confidence. It takes so much to make me believe that I'm actually kinda sorta not sucky at something. Programming kinda made me feel that way. I haven't written much here lately because I've just been so busy trying to keep my head above the water in school because what we've been doing in school is nothing. The "teachers" I've had have been so inadequate that going to school felt like a gigantic waste of time. I've been in need of a lot of tutoring from the nice guys at StackOverflow. They've been really kind to me and taught me so much.

But right now I feel like the dumbest person on earth. Nothing has worked for me today; the tabpane doesn't resize vertically even though I've set everything properly (what is it I'm missing?!), I had to reinstall MySQL, I can't get cygwin to move into the Program Files directory and I've manage to really test the patience of my really kind and helpful internet friends.

I don't even know what a project like the one I'm trying to build is supposed to look like. I've been reading so much SQL theory that I feel like I should know this already, but I haven't got a clue on where to even begin to put it into practice.

I'm sorry, but I just needed to write that. I hope I'll feel better soon. I'd like to think that something good always happen after something bad.

One can dream, right?

It would be nice if I could manage to get a job working with Java already; I love coding and it feels like I will learn more and become a better coder if I get to go out into the real deal business. I'm going to a gathering on thursday and I've been toying with the idea of making a website for myself to have something to show myself off with.

It would be nice indeed if someone thought I was of the right material to hire or train through a paid internship...

So the design I've worked up so far looks something like this:

"For dummies" is not for dummies

And it's definitely not for smarties either. I'm reading a book out of the series "for dummies" and it really baffles me how bad this book is. I already kinda have an idea about what the subject is about, and I know most of the best practices for the tasks described in them.

If you are struggling with a subject and want to learn more about it, do not buy a "for dummies" book. It will only make you feel more dumb and confused than you already are. And it's NOT because the book is overly complicated; it's just poorly written.

I've just shifted through 40 pages of utter and pure bull that won't teach you anything and has little to no relevance for the subject you're studying. It includes a role-play and a long rant of how awesome you're gonna be when you've read this book. It isn't, because following those 40 pages, is a on-and-off continuation of the role-play mixed with bad implementations of the code. They show you some concepts of the subject at hand but never really explain what the red thread for the subject is.

The pedagogy is null.
The facts are null.
Any pattern for the concept is null.

I'm getting an awful lot of NullPointerExceptions from a book that's supposed to to teach patterns, design, and structure.

And that is an issue because the readers the book is targeting can not tell that the information is faulty, that the pedagogy is bad or that it isn't their fault that a book marketed "for dummies" makes them feel more stupid. That's a horrible trait for a book to have, and it strongly discourages people from learning. You shouldn't have to feel that you're too dumb to learn something just because you read a bad book.

The only dummies relating to that book, is the one who let the books be published with such poor and confusing content.