Hacker Newsnew | past | comments | ask | show | jobs | submit | fayimora's commentslogin

While this is true, I just feel like there isn't enough help out there. I know a few people who are security conscious but are not sure what they really need to do to "protect" themselves. Loads of articles out there but most of them require a certain level of familiarity with tech which is not very appealing to the uninitiated.


Well true the help needs to be increased. Programs like National Cybersecurity Awareness Month need to be popularised more. Also most people are not updated with what's happening and what news threats are popping up everyday.


Wow I have been using Twitter since 08/09 and I never knew about the ".@" reply.


There was nothing special to them though. Convention was just ".@user" but you could also have used "Hello @user!" The point was to force Twitter from treating it as a recipient-only message.


The way I understand it, the 140 character limit still holds. They just stopped counting things like mentions and URLs.


But if they didn't use a misleading title you wouldn't have clicked the link...


haha I thought about that too. Clever but slightly misleading. Surely they could have come up with something true and equally attractive but then again it's the battle of "who gets the story out first"


Is it misleading to call a spade a spade? There's a character limit, they're just going to arbitrarily decide what is and isn't a character based on engagement feedback they get from advertisers.


interviewer: How far are you intending to take this? me: Oh, just two layers deep

haha


I would have given him the job


If that were a real situation, I wouldn't have, he over-engineered the shit out of it and while cool, I prefer devs who can solve simple problems simply; they get more work done for the price.


This is not over-engineering. Defining a couple of functions to solve it would be over-engineering, like offloading Fizz to it's own function, Buzz to another one etc. Anything (deliberately) more is just comedy.


Training a neural network to solve fizzbuzz is over-engineering, fun over-engineering, but over-engineering none the less.


Depends on the position no? If you are looking for a developer sure. But if you are looking for an engineer, creative solutions are a plus.


Sometime it is better to hire for culture, someone who is intelligent but also, and this is critical, can take a joke.


Yeah, I suppose the guy wouldn't feel good in the company anyway. Personally, I wouldn't either. Sense of humour is an essential part of good dev environment, IMO.


Which is why I said if this was for real.


I prefer employers that don't treat me like a baby, so to each their own ;)


Well, when you give a hilariously bad interview question...


It's not a bad interview question, if you think it is, you perhaps haven't had enough experience with candidates applying to programming jobs who talk a good talk but can't program to save their lives.


Well, technically, as a programmer and not enterpreneur you shouldn't be expected to have "experience with candidates applying to programming jobs who talk a good talk but can't program to save their lives".


No one said programmers were expected to; however, not having that experience makes judgement of what is or isn't a bad question baseless. FizzBuzz and all such trivial code tests are fantastic interview questions because most applications can't program, that is exactly the point and purpose of FizzBuzz, weeding out liars of which there are many due to high salaries in comparison to other fields.


Yeah, hopefully this kind of question is handled in a phone screen before bringing them in.


I can't seem to get past the captcha :( Anyone else?


Me too. It seems to depend on browser. I did not pass on Chrome but pass after switching to Safari.


Very weird! I just tried in Safari and all I had to do was tick a checkbox as opposed to identifying pancakes and street signs in Chrome.


I was going to ask the same. I usually just pipe my content to the gist command/tool.


THIS! That diagram is just ...


Don't want to show off, but it seemed quite readable to me, once you notice that the arrows have numbers..

It shows many interesting details (the only API command seems to be Patch. There are two sync phases on the client, one to determine what to send to the server, one to determine what to merge upon server response). I quite like diagrams :))


What do the numbers represent?


Lifecycle of data as it changes, apparently.


The diagram is horrible and doesn't really explain anything. I want to know what it is, not stare at some cryptic diagram for ten minutes.


Maybe or maybe not. Am assuming that is just a typo. The author most likely meant something else but you must admit that the idea of writing iOS apps using ruby is awesome.


This is PROGRESS!


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: