HNHacker News
TopNewBestAskShowJobs

elohesra

346 karma · joined October 17, 2013

submissionscomments
elohesra··on The Internet mystery that has the world baffled
Genuinely made me laugh. I always crack a smile when I see someone use the "you probably wouldn't get it" cop-out (yes, I realise you're making a mockery of the concept) to avoid explaining something that they evidently don't understand either. I seem to see this fairly often in large, complex fields like mathematics or complex systems programming from people who either have an agenda or are trying to bullshit their way through a job for which they're under-qualified.
elohesra··on Why Mac users don’t rant about the OS
First point was correct, other two weren't. It was basically a jab at how terrible the Windows 8 UI overhaul was, rather than a boast about how great the Mac UI is.

EDIT: Incidentally, the Windows 8 UI overhaul was terrible. Really terrible. I mean, that does need to be pointed out. Apple got a lot of stick for some slight changes to the way their icons appear on the newer version of the iPhone (forgive me, I'm not an Apple user so I can't comment, I just know the word 'skeumorphism' was thrown around with various levels of anger), but Microsoft seemed to get a much quieter and meeker acceptance of their terrible UI overhual. Yes, there were articles at the time saying "what is Microsoft thinking?", but it seemed -- at least to me -- to just be wearily accepted that Microsoft had dramatically changed their UI so that it was unusable for anyone coming from a previous version of their OS.

I'm not really sure why there wasn't more consumer outrage about Windows 8. Every Windows 8 user I speak to hates its UI, but they just seem to hate it and get on with it. Maybe it's because Windows users are generally less excited by their OS than Mac users? I've never really known a Windows user to speak at any great length, positively or negatively, about their OS.

elohesra··on Show HN: MMORPG in 55KB of Javascript
Um, when I try to access the site, I get this:

http://gyazo.com/8b0d0be033b42c789cbfde821fc7a7e1

For posterity's sake, I'll explain the image: it's Norton blocking the site, citing an extremely vague 'drive-by download' threat:

http://safeweb.norton.com/report/show?url=http:%2F%2Faberoth...

The site owner may want to get in touch with Symantec to figure out what's going on.

elohesra··on Show HN: My new project - ask.io
> Cool your jets, man. It wasn't meant to be offensive.

Please do not tell me to 'cool my jets'; this isn't 4chan. Now that the parent has explained what she meant, it's clear that it had nothing to do with conflating Woman and Adult.

That said, if it had meant what I thought it meant then it would have been worth calling out, whether offense was intended or not.

elohesra··on Show HN: My new project - ask.io
Ah, and with the link further down to the TokenAdult username, it all makes sense. It was the link between Woman and Adult that was baffling me, as I've not been around the HN comments long enough to know who TokenAdult is.
elohesra··on Show HN: My new project - ask.io
Apologies, maybe I am misunderstanding this point:

>Sigh...sometimes I wonder if I shouldn't change my username to "tokenwoman", a la "tokenadult". :P

But are you suggesting that tokenwoman is synonymous with tokenadult, and by doing so suggesting men are children? If so, I consider this insulting rather than amusing. Sexist jokes are unwelcome regardless of the gender being targeted.

If I've misunderstood you, then so be it.

elohesra··on Show HN: My new project - ask.io
I agree that it wasn't exactly posted in a tactful way, but I actually broadly agree with omeid2's assessment. What is this site other than a very simple data-entry page with an (entirely uncustomized) bootstrap theme on top of it?

I appreciate the concept of getting a feel for the market on an early (very early in this case) alpha, but I don't feel this is productive for HN. I mean, how simple are we going to allow ShowHN to get? A single static page with an H3 tag and the text 'good site coming soon'? I mean, that'd require some work -- almost none, but some -- so should we just say "The OP worked to create this, so I'll give feedback instead of pointing out the obvious and saying that the OP needs to put more effort into ShowHN submissions"?

Frankly, this feels like an AskHN masked under the guise of a ShowHN. I felt almost duped by the site, as if I were looking at the earliest skeletal structure of a site and being asked to rate it as if it had had significant development time applied to it. Maybe I don't understand HN well enough yet, or maybe I'm just cranky from working 27hrs straight, but that's my honest feedback.

elohesra··on Never Heard of It
Ah, I was half debating whether or not you were being sarcastic, but I spend a lot of time in feminist communities, and a lot of the people there say a lot of things like that (they don't really seem to have understood feminism much).
elohesra··on Never Heard of It
I honestly don't even know what to say to sexist drivel like this. Since several replies to the parent have gone along the same lines of making overly generalizing misandric statements that would be rightly called out as sexist gibberish if said about women, I suppose I'll just reply to this most egregious of the lot:

Where have all the smart hackers gone who're so quick to point out that society is at fault when negative characters of overly-stereotyped women are raised? If I were to play their role -- and tacitly accept this farcical charade that men are all bluster and ego -- I'd point out that the reason that some men might be less inclined than some women to admit they don't know the answer to something is that they know that they'll be held accountable for not knowing that thing. In this stereotyped version of reality over which we all seem to be forming a merry echo-chamber, women are unlikely to be brutally admonished for being wrong or incompetent (perhaps because those around them expect no better of them, due to negative stereotypes). This gives them the freedom to admit they're wrong, or that they don't know a given thing. Men, on the other hand, will be held accountable for their lack of knowledge, making it a much riskier endeavour to admit they don't know something.

Of course, this entire commentary presupposes that this phenomenon even exists. My team (half male, half female), shows this 'desire to be seen as knowledgeable' as a corollary of age and gender combined: the oldest member of the team never says 'could you explain that to me', and always attempts to BS his way through conversations, but the younger 20-something aged male members of the team are perfectly happy to admit it when they're out of their depth. Maybe this is unique to us? I doubt it: somehow I expect that this stereotype -- much like all other common stereotypes -- is overly broad and downright moronic.

elohesra··on Vi Hart: cramming G+ into YouTube has made comments even worse, I'm leaving
And yet it's allowed me to call myself 'Bruce Wayne' ever since they started with this real-name crusade.

Honestly, the chilling effect worries me. I appreciate that a lot of people would rather just not deal with the like of Stormfront, and simply pretend to themselves that people like that do not exist, and that those views are not held, but this is a harmful way of dealing with anti-social views.

Even if we argue that a real-name policy would totally kill off all hateful comments, we have to consider if this is even a good thing; hateful comments should be met with rational arguments that undermine them, and show them to be incorrect. If someone says "all [people of some class] are evil", then one solution is to shame them into shutting up by linking their comment to their real name, but this just allows them to continue to think this way without ever hearing a dissenting opinion (I mean, they're hardly likely to bring this up in public, are they?).

The internet has a wonderful power to throw people of contrasting views together, and get them to show each other how they think, and allow them to change their minds. The mere fact that this process may sometimes result in offense isn't a good enough reason to stop it. If someone's views offend you, then it is your duty to prove them wrong and -- if you cannot do so -- consider that your own views might be incorrect.

I know I've personally debated with others online and learned from the experience, and I also know that I'd never have done so were it the case that I would have had my real name linked to the views I was espousing. It strikes me as incredibly harmful for society in general to attempt to silence offensive speech, not only because it means that those who hold offensive opinions can never be proven wrong, but also because it means that unpopular, yet true, opinions have no platform to be proven right.

elohesra··on They want to hire me. What should I do?
This is actually a very good idea in general. If the programmer left because of some sort of perceived problem, and the company doesn't see the perceived problem as actually being an issue, then they're unlikely to change their mind when you join. If the programmer left over something that's also going to upset you, and the company doesn't agree that they need change, then it's a bad idea to join.

Alternatively, if the company also perceived the problem as an issue that needed solving, but were -- for whatever reason -- incapable of doing so, then they might be worth a shot. Just don't join and then expect them to change the way they do business in order to suit your needs.

elohesra··on They want to hire me. What should I do?
Find out why the other programmer left. He left knowing full well that it'd leave the company in the lurch, and that's a pretty bad sign because it means that they've upset him enough that he doesn't care about hurting them.

Giving some basic armchair analysis, I'd assume that the mathematician gets a lot of kudos for his 'genius' inventions, and the programmer is treated like a second-rate code monkey who's just there the aid the oh-so-godly mathematician. If this is the case, then it's obviously not worth joining, but make sure to find out why the other programmer left.

elohesra··on Questions to ask your potential employer
I personally think #2 is quite important: it proves the employer knows why they're employing you, and that they have thought about the scope for career growth in the role. If the employer hasn't got a clear idea of why they're employing you, then your role becomes an amorphous "do whatever I want done" job, that won't necessarily meaningfully contribute to your skills or remain interesting. If the employer hasn't thought about the scope for career growth in your role, then that -- to me -- shows they don't value their staff enough to care about whether they get anything more than a salary out of the job.

I think it's a little strangely phrased (sounds a bit obsequious), but I think it's a valid and important question.

elohesra··on Why Do Brits Accept Surveillance?
Thanks a lot for the in-depth reply!

It's interesting, because I think most people seem to assume that the power dynamics of working at GCHQ is somehow fundamentally different to those of a private company: because GCHQ spies on the public and is above us in power, everyone at GCHQ must also be on some sort of equal 'spy-level' footing and equally aware of what's going on. Of course this obviously isn't true, and I expect it's much as you describe i.e. it's like a regular company where no-one really knows anything above their pay grade.

Also -- assuming you've not already thrown the account away -- could I ask how many of the technical people at GCHQ appear to be working there for moral reasons vs working there for the challenge of it? Are there many techies who consider it a moral prerogative to work there?

elohesra··on Why Do Brits Accept Surveillance?
Assuming you actually do work for GCHQ, would you mind elaborating (briefly, and without violating official secrets) why you've chosen to work for GCHQ, and how you feel about the Snowden leaks?

Does the level of spying targeted at the population bother you, or do you feel it's justified? If you're not able to answer this question -- e.g. it may implicitly confirm official secrets -- then would you mind briefly summing up how happy you are working for GCHQ post-Snowden?

elohesra··on After traffic stop, man forced to have x-ray, enema, anal probes and colonoscopy
Thanks for linking that. It appears that we've found the real reason the officers decided to put the man through this ordeal:

(Excerpt from complaint -- emphasis mine) 24. Plaintiff asked Defendant Rodriquez if he was free to leave, which Defendant Rodriquez contends that he found rude. 25. Defendant Rodriquez told Plaintiff he suspected Plaintiff of having illegal drugs in his car and proceeded to interrogate Plaintiff on the matter.

The officer felt that he'd not been shown correct respect by the victim and then decided to make him pay. To be honest, I'm not sure how much I blame the doctors in this fiasco, because I don't know what sort of legal protections are available to them if they were to refuse to carry out the invasive operations. Do doctors in the US typically have a legal counsel who can advise them if a warrant is valid, or what operations an officer with a warrant can demand? I know I'd have no idea if a warrant were valid, or what the officer could compel me to do.

elohesra··on Goodbye R scripts, hello R packages
With regards to piping, yes this can sometimes be true. It's very dependent on the actual program. Programs on windows take a string array as the argument to their main function, so if the program is written in such a way that it iterates across every element of the string array argument and then does something with them, then this'd work. Most of the Microsoft programs behave sensibly with this, and execute an Open command against each of the files dragged onto them, but this isn't guaranteed to be true.

I'd still like a nicer, general purpose way of manipulating multiple files in Windows. That does seem to be one place where it's definitely lacking, but it could just be that I don't know how to do it.

elohesra··on Goodbye R scripts, hello R packages
Very interesting, thanks for the in-depth explanation.

I think that this does appear to be a fundamental difference between Windows devs and Unix devs. All of the things you've listed there, I'd do through the GUI on Windows.

Searching, obviously, I'd Windows+E (or Super + E in OS non-specific keyboard terms) to open up the explorer, then tab+tab to navigate to find, then type the query. I can't think of an easy way to pipe a set of files into some sort of function (e.g. for substitutions) outside of F#, maybe something exists for that in PowerShell, but I find PowerShell to be a bit of a poorly-documented mess.

Source control, again, I'd do through the GUI. With TortoiseHG, I've got my hg commands available for me with the right click of a file/folder under a repository. I see that it seems that this'd be significantly slower than doing it through command line, but the windows shortcuts actually make it pretty snappy to navigate through the file system in the GUI.

For kicking off a VM, I'd usually attempt to shortcut the command I'm looking to execute regularly and then Windows+D my way to the desktop to execute it.

Windows does seem to have made the decision early on (i.e. back in '95, when I first started using it) to provide a clean and concise GUI first and foremost, and then to add programmer/automation-friendly terminal APIs as an afterthought. I wonder if the issues that Unix users on windows have are caused by the fact that Unix systems seemed to go the other way, and that attempting to replicate a Unix experience on Windows would just lead to frustration?

This is interesting, because I rarely get a chance to use Unix at work, nor do I get much of a chance to speak to Unix devs (we're a Microsoft shop -- WPF, ASP.NET MVC, and SharePoint if we're feeling masochistic). Thanks again for an interesting snapshot into your workflow.

elohesra··on Goodbye R scripts, hello R packages
Thanks for the reply.

That does make sense. As a C# developer, I haven't really had call to use OSS IDEs, so I can't really comment, but I do remember having an ugly time trying to use an OSS interactive disassembler on Windows.

elohesra··on Goodbye R scripts, hello R packages
Thanks for the reply.

What sort of command line tasks are you trying to invoke on both systems that are easier to invoke on unix? I can't think of any commands off the top of my head that I've had to invoke recently, other than IIS commands. Maybe it's just the fact that the C# developer's workflow is so heavily IDE based. I can imagine that if you were having to manually invoke the compiler etc, then a useful command line would be a must.

elohesra··on Goodbye R scripts, hello R packages
Purely out of interest, what's so wrong with Windows as a development environment? I've seen this claim touted before on HN, but I've never seen an explanation (not doubting that there is one; I just haven't seen one). I develop on Windows every day, and I'm always happy to learn a new way to improve my workflow, so does Ubuntu (or Mac) actually make it easier to develop software, and if so then how?

I'd also be interested to hear what kinds of software you've found it hard to develop on Windows.

elohesra··on Are You A Typing Hacker? Prove It
Great (or perhaps just lazy :p ) minds think alike. After about 25 levels I started inspecting the javascript for ways to break the game, rather than playing the game properly. It turns out that the game keeps track of all the entities on the screen (both player and NPC/enemies) as an array, and that on each call of draw it checks if any are still alive, and if the player has collided with an enemy. It doesn't actually check if the player still exists, or if there's any way that the enemies could have been killed. As such, replacing the draw function with:

ig.game.draw = function (){this.backdrop.draw(0,0);var d=this.lastKillTimer.delta();ig.system.context.globalAlpha=d<0?d*-2+0.3:0.3;for(var i=0;i<this.backgroundMaps.length;i++){this.backgroundMaps[i].draw();} ig.system.context.globalAlpha=1;for(var i=0;i<this.entities.length;i++){this.entities[i].draw();} for(var i=0;i<this.entities.length;i++){this.entities[i].drawLabel&&this.entities[i].drawLabel();} if(this.mode==ZType.MODE.GAME){this.drawUI();} else if(this.mode==ZType.MODE.TITLE){this.drawTitle();} else if(this.mode==ZType.MODE.GAME_OVER){this.drawGameOver();} if(this.menu){this.menu.draw();} if(ig.game.entities.length > 0) { while (ig.game.entities.length > 0) ig.game.entities.pop();} }

causes you to auto-win every round. Just goes to show that, as per usual, programming hacks for the game is more fun than the game itself. Programming vs anything else? Well, programming is gonna win every time.

EDIT: In case it isn't obvious, it's the last line of the function which I've modified:

if(ig.game.entities.length > 0) { while (ig.game.entities.length > 0) ig.game.entities.pop();}

So, for each call to draw, the game will run as per usual and then end the call to draw by popping all entities from the entities array, which ends the wave.

elohesra··on You don't need millions of dollars
If it is called sexist for that reason, then the person using the term 'sexist' to describe the situation is comically misunderstanding the term. Sexism is basing one's beliefs about another on the basis of their sex, even if those beliefs don't actually relate to sex in any meaningful way. For instance, saying "The IT industry requires you to work hard, so women won't like it, because y'know, women can't stomach hard work" would be incredibly sexist. Conversely, saying anyone is free to join the IT industry is the exact opposite of sexist.

Unfortunately, there seems to be a bit of a misunderstanding around what sexism actually is: it's not sexist for something to simply not be favourable to some sample of a given sex. In order for something to be sexist it either has to make assumptions about the qualities of a given sex based only upon their gender, or be discriminatory toward a given sex based solely upon their gender. Discriminating on the basis of hours worked is the opposite of both of these.

elohesra··on Coding Interview Tips
I'm not sure we mean the same thing by 'boring'. Boring, to me, doesn't mean that the person doesn't have hobbies, rather it means that the person is a perfectly nice person who just doesn't gel with the team. In fact, 'boring' is probably the wrong word here: it should probably be something closer to 'outsider'. That said, larger organisations do depend upon outsiders to prevent groupthink, so this is a multi-faceted issue.
elohesra··on Coding Interview Tips
Personally I wouldn't mind working with him as a fellow employee, but he'd make me nervous as a manager of a small business. He sounds like he's great at his job, but has zero emotional ties to it, which translates to him being less likely to weather any bad times the company may face.

Ultimately, you clearly agree that gaining and retaining great talent is what makes a software business stand ahead of its competition, so isn't it risky to gain someone who isn't going to feel bad about leaving the business (and take all his experience with him)? If I can hire someone who'll fit in well with the team and produce good quality code, then I'd consider him a better long term investment that someone who fits in poorly with the team and writes great quality code, purely because the latter person has fewer reasons to stick with the business than the former.

elohesra··on Coding Interview Tips
I think it really depends upon the business. I mean, a genuinely bad programmer, who doesn't merely fail to positively affect a codebase but actually manages to worsen it, will be bad in any programming business. However, many software shops just won't see the return on having a superstar. For instance, consider a shop writing Excel VSTO plug-ins: it's not wildly difficult work once you've done it a few times, but the work is time consuming, so it'd make more sense in that business to have good programmers who can work together and cover each others' backs than it would to have one brilliant programmer who annoys the rest of the team into leaving, or bores the rest of the team into losing what little enthusiasm they have for an already fairly boring niche of software development.

It may not make sense to choose personality over technical chops if you're trying to hire a language designer, but it may make sense to do so if you're in a niche which requires teamwork.

elohesra··on Coding Interview Tips
I suppose the answer can only be supplied if we know more about you as a developer, and as a person. If you're a perfectionist, then it could well be that your previous projects are perceived by others to be of better quality than you yourself perceive them. A perfectionist could well consider a project 'unfinished' if it doesn't cover improbable edge cases, for example.

However, assuming that you're accurate in your statement that your projects were unfinished, then it would appear that you need to question why that's the case, as we cannot infer that the traits you've ascribed to yourself are the cause of project failures without knowing more about the other variables in the equation. For instance, the projects may well all have been failures for no fault of your own: scope creep, management interference, poor teamwork (or poor team members), or any number of other variables could be responsible. But since this is not something we can address at this point, let's assume that your project failures are indeed a result of your perfectionism.

The easiest way (in my experience) to 'cure' perfectionism in software is to follow the YAGNI ("You Ain't Gonna Need It") mantra, coupled with approaching a project from a divide and conquer perspective (yeah, pg would pretty much hate this). First break the project into its key deliverables and its 'nice to haves'. Once all the key deliverables are complete, then the project is complete; 'nice to haves' aren't factored into the completeness equation for the project. Once you know what your key deliverables are, then order them in terms of dependency: if deliverable A requires that deliverable B be completed before deliverable A can be completed, then focus on deliverable B first. Now that you know what you're supposed to be working on, you can get started on the deliverable at the root of your dependency tree, but whilst working on it ensure that you're only adding the functionality necessary to complete the current deliverable. As you work your way through your deliverables, refactor the previous deliverables as necessary to make your current deliverable work. For instance, if your root deliverable wasn't required to be thread-safe when you first wrote it, but your new deliverable requires it to be thread-safe, then work your way back through your deliverables refactoring as necessary in order to meet the requirements for your current deliverable.

By sorting your deliverables into dependency tree, you can ensure that you can properly apply YAGNI. It's very tempting for a perfectionist to turn into an architecture astronaut, and spend weeks or months mapping out the entire solution and all its edge cases before they've even started to work on a single deliverable; by keeping your deliverables in a dependency tree and working from the least to the most dependent, you force yourself out of this mindset. By applying this method, you also force yourself away from analysis paralysis, because you're not permitting yourself to consider patterns or architecture until the project's current deliverable necessitates it.

It's worth noting that this method won't work for all projects, as it requires a good understanding of what the deliverables for the project actually are before you can apply it. It also may not work for you at all, since it's all down to personal experience, but I've personally found that forcing yourself to focus only on the concrete deliverables ensures that you don't end up stalling yourself in analysis, and gives you lots of little pep boosts in the form of finished deliverables and refactorings.

Nonetheless, good luck finding a cure that works for you.

← PreviousPage 3 of 3