HNHacker News
TopNewBestAskShowJobs

rilita

68 karma · joined December 3, 2014

http://www.rilita.com
submissionscomments
rilita··on Should U.S. Hackers Fix Cybersecurity Holes or Exploit Them?
Considering that when I found some large holes and reported them I was then harassed by the FBI and given nothing... I think hackers should exploit the holes and then sell them to the highest bidder.

Helping protect people just gets you harassed.

rilita··on Your Brain Can’t Handle the Moon
After the first couple of paragraphs my own analysis is this:

1. Distance in the mind is based on cues; 3d binocular cues only work at distances less than a mile or so. Beyond that your mind depends on relative reasoning to know 3d structures. A moon close to the ground will connect to the ground you see and be placed at the furthest possible distance. Anything at that distance is made to feel larger in the mind.

2. If you look at a moon up in the sky, there are no cues to indicate how far away it is or anything.

3. A moon up in the sky is surrounded by empty space. Lots of empty space will conceptually "crowd out" the moon and make it appear smaller not larger.

I then finished reading the article. Conclusion of researchers: #1. Good joy guys? ...

rilita··on Do we really still need a 32-bit JVM?
Article more or less: "I don't think that we do, so I tested it a bit. Tests confirm my assumptions. Still; there are cases where 32 bit is faster. I won't bother to explain why."

As usual "All headlines that ask a question can be answered no" ( but inverted to make it more confusing ). Really the title of the article to fit the mold should be "Can we get rid of the 32-bit JVM?"

Really what should be done is take the algorithms from language competition website, and then test all of those on 32-bit versus 64-bit with different data sets. A few tests is hardly conclusive or explanative of what is fast and what is slow.

Obviously a raw call to nanotime will be slow. Do you really need nanotime? If you don't; is a lower precision call faster than nanotime?

rilita··on My first job burnout
Seems like a great candidate to hire onto a job where you intentionally burn people out. She is willing to work 11 hour days, get burned out, and not blame the employer. Lets hire this person. Surely we can get a good year of overwork before the next burnout. Then maybe a cool "The 2nd time I got burned out" article.
rilita··on My first job burnout
That's why you should sleep at your desk if you are tired; it is much healthier than getting sick and fainting. Plus; you can wake up if anyone makes enough noise and quickly get back to pretending you are working.
rilita··on My first job burnout
Please put "Will tell the truth in all situations regardless of the effects" on your resume. Let us know how that goes for you.
rilita··on My first job burnout
You imply that because the people who did talk to you did not google you, that no one does. It is more likely that the people who do google you do not give you an interview.
rilita··on My first job burnout
I've worked for multiple companies that intentionally burn out their workers. I even posted negative reviews on glassdoor with my real name. The companies just had glassdoor remove the reviews to appear positive. There is nothing you can really do about bad employers except try to avoid them or escape from them if you end up in one.
rilita··on My first job burnout
I agree with this very strongly. Be very careful what you post about yourself online that is associated with your easily searchable name that you put on job applications. Burnout may be a real problem, but stating you think burnout is somewhat normal and that you will occasionally need time off to recover ( like op seems to state in article ) is not going to win you any high stakes high reward positions.

Agreed also it important to have continuous work listings on your resume. "I was laid off and it took a bit of time to find a good position" is usually the easiest excuse for <3 months of time off.

rilita··on My first job burnout
The article seems curiously devoid of explanation as to what caused the burnout. As a result there is no reasoning in it really as to how to avoid burnout. ( besides "take a break when you need it" )

It seems to imply that burnout is a failing of the employee not of the employer. I disagree with this notion entirely, as I think management has a duty to care for and protect their employees from burnout. That is why there is always a chain of responsibility, so that this can occur at all places on the chain.

A properly functioning corporation will help their employees avoid burnout and not make demands of them that inevitably cause it.

rilita··on Show HN: My reply to LinkedIn recruiters
You would be surprised at recruiters tolerance for being told off. I have experimented with some and they actually take it very well. They are human beings, as long as you are real they will respond in term.

I don't say something like that until they know me a bit though. I have asked my current consultant group "What happens if I tell you to fuck off?" The guy responded "Well I wouldn't like it, but you do your job well and I wouldn't take it personally."

rilita··on Show HN: My reply to LinkedIn recruiters
"I have a low tolerance for bullshit" You should totally add that to your resume. I am sure it will get you far in life.
rilita··on Show HN: My reply to LinkedIn recruiters
Recruiters typically make a percentage based on what you end up getting paid. It is in their best interest for you to be paid more not less. The only reason they would pay less is to try to get people into a position to which they don't otherwise fit well.
rilita··on Show HN: My reply to LinkedIn recruiters
I have interacted to a meaningful extent with at least 10 different major recruiting firms, and I can tell you that it varies greatly. There are lots of ones that suck, but some of them are actually quite good and respond well and work for you if you actually talk to them and explain what you are looking for.

Hating on all recruiters since a large percentage of them suck isn't fair.

rilita··on Show HN: My reply to LinkedIn recruiters
I've seen people happily work at much lower pay then they deserve. I've also seen people work at higher pay then they are worth and still be miserable. Pay isn't all that.
rilita··on Show HN: My reply to LinkedIn recruiters
Note I did not say that I would not pay my developers what they are worth. I am saying I would not put it out there initially in emails. If I stated I pay well publicly it would just attract money grubbing morons.
rilita··on Show HN: My reply to LinkedIn recruiters
We don't need more tech people. We need more tech people who give a shit about their jobs besides getting paid.
rilita··on Show HN: My reply to LinkedIn recruiters
Yes it is. Many companies doing direct hire ( going past recruiters entirely ) will drop you as a candidate entirely if you ask for salary too soon in the process.
rilita··on Show HN: My reply to LinkedIn recruiters
While I agree you need to know the company before accepting; the goal of recruiters primarily is to give you some limited information and then see if you are willing to talk on the phone. A short phone call is the best most efficient way to handle recruiters. You can have a frank conversation and determine exactly how valuable they are in a short period of time.

Dragging on initial email crap does not truly handle the situation.

As stated already, I think a range is reasonable. Asking the exact number is not.

rilita··on Show HN: My reply to LinkedIn recruiters
Recruiters don't merely pass on resumes. They work hard to find viable candidates and to tolerate their crappy attitudes when they are trying to help place people in good jobs.
rilita··on Show HN: My reply to LinkedIn recruiters
I agree it is reasonable to share the company name once you express interest. It is not reasonable to need it to decide whether you will even speak to the recruiter.

If your desire is just to weed out recruiters, why not just say "fuck off" and see which ones still persist. This is nearly equivalent.

The whole attitude of "I want to know the salary since I intend to switch again in a couple of years" is exactly why I wouldn't hire people with this attitude.

rilita··on Show HN: My reply to LinkedIn recruiters
I would never hire someone with this perspective. Quality of the position and the ability to enjoy it and work hard without stressing is way more important than pay in my book.
rilita··on An Analysis of Nespresso
I have used many varieties of coffee machines. I do have a nespresso machine amongst them, and it seems to work quite well. The volume of espresso/coffee it produces is low per unit time of water running through the coffee though.

When I use a normal espresso machine, with my own tamped grind, it puts out espresso/coffee at a higher rate, and I find it is smoother/less bitter due to that.

I do tend to prefer a less strong cup, so for me it is nicer to use my own grind as I can vary: 1. The quantity of ground beans 2. The fineness of the grind 3. How much coffee I get by how long I pull it. ( I realize running it too long will make it bitter )

In the article I am gathering he is measuring what percentage of the "grind" is removed in the process of brewing?? It would have been nice to see this compared amongst a variety of machines, not just 1 nespresso machine and 1 manual drip. Also an acidity test of the resultant coffee would be neat.

For the interested, here are the various machines / methods I have used:

1. Standard junky drip machine ( yuck... )

2. Bodum dual glass bowl vacuum I find this to be the strongest method of brewing, but it also makes the coffee way too bitter for my tastes.

3. Keurig machines Have used 5 or so different ones of these. The higher end commerical ones tend to be a little better but mostly they produce weaker coffee and let a lot of grounds through into the coffee. I don't think the water is hot enough from these, nor is the pressure high enough to get crema of any worth.

4. Tassimo machine This is my favorite taste thus far. The programmed t-discs allow the setting to be varied ( heat and brew amount ), and has produced the smoothest coffee I've had of all the machines I have used. I own 2 of these machines. My only complaint is I cannot use my own grind.

5. Senseo This is my favorite machine overall. The pods are small cloth bags, and the pressure seems to be high enough to produce good crema. Also; I can use my own grind in reusable filters that go in it. Great consistent taste and very easy to use. Also; very easy to clean the whole machine. I own 4 of these. ( for extra parts )

6. Starbucks "instant" machine. One company I worked at had a huge automatic like starbucks branded machine. This thing tasted horrible. The coffee was the most bitter I have tasted from any machine. It also tasted like it was never cleaned and had a high amount of grinds left in the coffee.

7. Super automatic espresso machine. Another company I worked at had one of the various $5000 automatic espresso machines. Unfortunately I forget the brand at the moment. It worked well, auto grinding etc. I used my own grind with it also. This was nearly equal to the taste/quality of using my own espresso machine, but I could not vary the tamp pressure. The auto internal tamping seemed too loose so the coffee seemed to have a bit less crema. It was convenient as it had less cleanup though.

8. Capresso EC100 This is my go-to machine that I use for my daily coffee. It is just a basic espresso machine. No real thrills here, but it has adequate pressure and heat. I grind my own beans to my desired fineness, add my own amount of beans to my taste at the moment, and typically brew like 4 shots worth out of the same tamped unit. This would seem to cause it to be more bitter but it does not and produces lots of crema. I also often rip open free keurig pods from work and use them in this machine. It improves their taste over keurig machines by far.

9. Old style large reservoir steamer with huge spring/lever. I picked one of these up from a yard sale. Takes forever to heat up. Needs to be cleaned constantly. Feels very finicky. I am way too lazy to be able to get anything consistent out of this. Far too much effort for little gains.

rilita··on Show HN: My reply to LinkedIn recruiters
Regarding your choice of fields:

1. Name - This is already in emails I get from recruiters

2. Email - Useful since LinkedIn emails typically don't include their actual email

3. Phone Number - Ditto to #1; they typically include it

4. How did you find me - Considering you stated this is in reply to LinkedIn recruiters; LinkedIn?? ...

5. Name of the company - Most recruiters will not share this information until you have gone through the process more. What is to stop you from ignoring them and contacting companies directly once they give this? This is a poor choice and will drive away recruiters. I do see this is not a required field, but that is not obvious at first glance.

6. Location - You should consider converting this into a zipcode lookup or something. If not generic information such as state or city may be entered here. ( or possibly nothing/bogus info )

7. Job title - Often recruiters have multiple positions available depending on your experience and fit. Also job title doesn't necessarily mean anything. Half of the jobs I have had had no job title.

8. Job description - This is usually provided in the email I get from recruiters. That said, sometimes they don't so I can see the use. You might consider adding "Required skills" as a question also.

9. Yearly salary before taxes - This is a required field. If I were a recruiter I would ignore you at this point. You should be more interested in the opportunity not the exact pay. This looks like a money grab. Having a good career is more important than a dollar figure. Better than this would be a set of ranges; then you can ignore all requests in the ranges you would not accept. Gets you similar info but avoids the insult.

rilita··on Deprecating the “X-” Prefix and Similar Constructs in Application Protocols
What is the point of "X-" prefixes? To make it clear that the thing in question is implementation specific and should not be relied on if you want it to work on all implementations.

Should "X-" things be created? Yes. If the people creating new implementations can't be bothered to make their changes official, or what those things does changes, then they use "X-". You should assume "X-" means "don't use this".

Why do the "X-" things persist and get implemented by everyone eventually? Because bureaucracy and standards groups suck and don't keep up with the times.

What does a standard group saying "don't use X-" mean? It is just a lame attempt by the group to stop people from doing things they aren't informed of or in charge of.

Guess what IETF: The people who care that you said this don't create "X-" things for the most part. The people who do are just going to ignore this.

rilita··on Facebook Messenger XMPP is going away
Email fails in the following ways:

1. Email client have vastly different feature sets and capabilities. Most notably, the HTML support is very different from one browser to another.

5. The vast majority of email systems do not even support encryption of the message itself

7. Large file transfer via email is horrible and extremely limited

8. No random chat support

9. No group chat ( cc doesn't count as it lacks history of the group chat )

10. Have you ever received emails seemingly full of gibberish? Utf8 not supported properly in majority of implementations. ( which imo requires getting and using a font that supports the codepoints )

11. No user index ( saying that you could have an address book also doesn't count; and that is a seperate thing which also there is no one spec that is used by all people using email )

12. No real time messaging support. Inherent in the discussion is that chat software is insant, not based on server polling.

rilita··on Worldwide DNS Performance
The site is very clean looking and it is entertaining to look at the results.

That said, there are a number of problems with this:

1. As stated by other people here, this is only from the perspective of where the tests originated, and is somewhat irrelevant once the DNS result is cached by your ISP.

2. If you are using any of a number of modern browsers, DNS will be prefetched before you even click on any link, so the DNS time from a user perspective will be zero the majority of the time.

3. The point of this was originally for choosing a good host for shared JS files. It is much more meaningful to use a distributed host with location based DNS to point you to the nearest fastest server, rather than just making the DNS request itself as fast as possible. Why do you think Google has so many servers all around the world?

rilita··on Worldwide DNS Performance
Would you mind updating your bar charts to say "Query time" instead of "Query speed". Some mention of the unit of the numbers would be nice as well, such as "Query speed ( ms/req )"
rilita··on Facebook Messenger XMPP is going away
IRC was essentially created 25 years ago. In all that time we have still to make anything significantly better.

Why does a system with the following features not exist:

1. Requires all implementing servers and clients to support the full protocol

2. Allows users to communicate to users on other servers ( not just users within a server )

3. Has free client open source reference implementations for native use ( C or the like ) and some web language ( Python & Dynamic JS )

3b. Has a free open source server reference implementation

4. Logging on the server indefinitely

5. Is always encrypted ( end to end via public keys, so that clear data never reaches the servers )

6. Offline messaging

7. Large file transfer with clean re-connection and continuation ( if neither party has a publicly accessible port, payment/membership to the server would be required to facilitate the transfer... )

8. Random chat

9. Group chat

10. Utf8 for full multi-lingual use

11. Index of users for finding other users

If someone would just create such a thing it would put an end to all the stupid shifting from one system to another from year to year. I'm getting tired of switching systems and reverse engineering shitty protocols in order to continue doing the same thing with less features.

rilita··on NSA is monitoring key Internet routers (1996)
Key portion from the article: "Puzzle Palace co-author Wayne Madsen, in an article written for the June 1995 issue of Computer Fraud & Security Bulletin (Elsevier Advanced Technology Publications), wrote that "according to well-placed sources within the Federal Government and the Internet service provider industry, the National Security Agency (NSA) is actively sniffing several key Internet router and gateway hosts."

edit: Title is better now; thanks.

← PreviousPage 2 of 5Next →