The bicycle thing is great, thanks for sharing.

Those that aren't "strict" in certain areas. Examples:

* Those without memory management (I'm not talking about garbage collection, though there seems to be a correlation). Buffer overflows/overruns and its cousins have caused many security flaws, including heartbeat and even flaws in java, where it interops with C programs for performance's sake.

* Syntactical leniency wrt. scope can lead to errors like apple's infamous "goto fail"

I agree entirely with the sentiments here, but I wouldn't consider it a security issue. A safety issue more like.

Security for software is typically defined to include things that protect you from loss of access risks. Think the latest ransomware that went out.

Specifically, the axes of security are integrity, authentication, and availability. Backups give the illusion of helping both integrity and availability. However, without practiced and verified recovery plans, they do neither.

In software in general, the past is the future. Things were going great, then everything went to shit in the 2000'nds.

Telegram rolls their own non-standard crypto protocol as I understand it. This is a bit of a no-no when it comes to security. More importantly; chat's arent' end-to-end encrypted by default (I can't find a way to enable it in the web-app), which means the telegram-whatsapp comparison makes no sense. Whatsapp is secure, telegram is not.

Also; end-to-end encrypted chats in telegram (they call them "secret chats") won't follow you between devices. A secret chat started on one device, won't be accessible from another. This makes them far less useful, and dissuades users from using them. Again; comparing whatsapp to telegram in terms of security is apples vs oranges.

You might not like this, but here are my honest thoughts: You seem to be selling yourself as a web designer, but your website is terrible, and so are it's contents.

I realise this is subjective, so I won't try and justify my thoughts. Frankly I don't care enough to debate them anyway, so you can take it or leave it, as you please.

Your designs aren't minimalist, they're just minimal; empty, underdone. And even then your colour palettes are grating. Not to mention that o23.io, days and skyler look pretty identical.

Maybe the reality is that no-one wants to hire you, because you, or the works you use to advertise yourself, aren't quite as good as you might think.

I should add that this is not meant to discourage you. As always in life, you have three options: 1. Be good. 2. Get good. 3. Get out.

I'm not saying you need to take option 3, I'm just saying maye option 1. is out of the question.

Your last sentence isn't necessary.

I changed it to something slightly less inflammatory.

Damn, I can only imagine what it was like before the edit then...

The ego on HN gets me every time. I quite like his designs.

Good for you, and good for OP. I'm really not trying to denigrate anyone, but OP is complaining that he doesn't get interviews. If his reviewers think like I do, using spans correctly in his html, and "playing the game" (which is what others are suggesting) won't do him any good.

His design is excellent for a developer. But maybe a little TOO minimal for a product designer.

I disagree. Maybe you are right, maybe this isn't the reason he doesn't get interviews, but if someone sent me that portfolio, I would not give the application a second look.

Probably not, but I did think a conclusion was necessary.

Fair enough. I thought the point about the sites looking nearly identical was strong enough to end on.

Well, thanks for pointing it out. Either way; an insult wasn't a good way to end it.

Are there any of those just-now-or.recently-switching devs in here? It would be interesting to hear their opinion, rather than guesswork.

This is my first week back on Linux after using OSX for ~4 years. I switched because it's cheaper. I needed more power and building a Linux desktop is way cheaper than buying Mac hardware.

So far: KDE is incredibly nice. I'm pretty blown away. Aesthetically I actually like it more than Aqua. The file manager is nice, the terminal is fine, there is a spotlight style search, virtual desktops, pretty much everything I would miss moving from OSX.

I miss 1Password the most. Right now I'm using a CLI client (passcards) to access my 1Password vault. I haven't setup notes yet but it seems like there are decent Notational Velocity alternatives. Relearning muscle memory to use CTRL instead of CMD is painful. I'm wasting a lot of time tweaking keyboard shortcuts.

Interesting. So for you the change was on desktop, not laptops. What changed you mind wrt price? I wasn't under the impression that apple computers have gotten more expensive than they were before?

Try KeePass, it works just about anywhere

Serious answer: Because many developers regard assembly as some sort deep magic only understood by elder gods. This, of course, comes from some vague (and not entirely correct) understanding of "assembly" running beneath everything else, and thus being fundamental, yet not immediately useful to a large category of developers today. Hence it seems important but archaic. Archaic + difficult = elder knowledge.

I've actually had a few coworkers think I'm some sort of elder god when I find the root cause of subtle bugs that would've either required deep knowledge of the C++ standard, or not-as-deep knowledge of Asm. These are bugs that others have spent many hours staring at the source and stepping through in a debugger without any better idea of why they occur, but are solved in minutes by a glance at the Asm. IMHO if you are working with native code at all, it's a very useful skill to have.

Even though it was a bit of a "sufferance", I enjoy having been full circle somehow. Starting with Java OOP in college, then went lisp maniac [1], then ml/FP. Which were all somehow further away from the machine, in a way. But at the same time lisp model seems a fairly thin layer over raw asm. And you realize that primitives of computing: arithmetic, logic, iterations.. are very similar whatever the language or paradigm. I then learned a bit about continuation, non determinism, compilation and now I'm almost free. A language is mostly an encoding. Most of them speak about the same things but in a different clothing.

Not 100% free, I think I need to finish my compiler training and forth bootstraping before I can claim that.

I can't really suggest others to follow the lisp, ml, prolog road though, so I'll just state what I wrote above.

[1] SICP especially, with its gradual pedagogy. From substitution, to environment, to register machines. You can see the relationships up close.

Everyone who works with native code, not just C or C++, should at least understand how linkers and loaders work.

Once you are tired being praised, teach them some valgrind. It will solve most of their problems.

I'm pretty sure the bugs I found would not have been valgrind-able as they were unrelated to memory errors.

From my experience most of the hard to trace errors come from uninitialized variables and they are usually valgrindable. It is VM-based so it can cache jumps and other conditions that depend one uninitialized vars via taint analysis.

Cool ! perfect explanation.

I don't like the aluminum bodies (as a matter of taste, I think they are ugly). But carbon fiber isn't functional. I've had a carbon-fiber-body laptop for ~3 years now. In that time, I've had to replace the fan twice. My bet is the flexible carbon fiber allows more bending than the electronics can actually handle. The flexibility also makes it feel cheap; why would i want a laptop that gives in when I type?