If someone puts all of this in the balance, you listen, and it won't leave you unmoved. Choose wisely whom you grant such power.
867 karma · joined November 18, 2010
If someone puts all of this in the balance, you listen, and it won't leave you unmoved. Choose wisely whom you grant such power.
This is the dark side of the (otherwise desirable) trait of "getting things done" as employee.
I you don't actively manage your working hours and hold yourself back, somebody else will suck you out until you have nothing left.
At the end, you will be very unsatisfied for some obscure reason: You did everything you was asked for, yet somehow noone appreciates you and you still earn entry-level.
In my opinion, you should only use 80% of your working hours doing the "real stuff". Devote 20% of your working hours to non-technical work, active career development and image management.
1) talk with your boss about clients
2) show interest in the business side of your project
3) ask challenging non-technical questions
4) have a nice chat with your manager about non-work stuff
5) make sure everyone knows who had the interesting feature idea last week
6) make sure that the decision which overruled your recommendation is in the meeting report.
...
This is good for you and the company in the long run.
Some of your tickets will have to wait, then. Maybe the deadline won't be met perfectly.
That's fine.
Consider a startup product on the finish line, which lacks polish because non of the makers is a professional designer. If they are like me, they do notice that the overall design is not professional/engaging/appealing enough, but are themselves not able to identify why exactly, and what to do about it. Thats where professional designers are sorely needed.
Me in that situation would not hesitate to pay you, say $600 (in european circumstances) to sit with me for 4 hours interactively, you giving advice and me tweaking the css/svg (the harder stuff for homework), provided
a) I am convinced you know you skills
b) You are able to communicate effectively with a non-designer
c) You could concentrate on the low hanging fruit: Limited effort which still improves my design significantly. It won't perfect, and doesn't have to be.
Note that for all of these points you would have to gain my trust, which is in itself a lot of work. Without that, I might still give it a try, but I would only willing to pay you throwaway money. But gaining my trust doesn't have to be one-on-one though, a good blog or your tutorials could do.
That's irrelevant for the question. The question is about the the value of HN regardless of its intended purpose (which is of course open to speculation).
To me, your tone seems a bit derogatory. I don't know if you intend to be that way, but if you were, please don't be. HN surely takes some effort and is hugely valuable to me, and I would rather have those who keep things running feel good about it. Even if it weren't perfectly altruistic, I'd say it's still a win-win for all of us, don't you think?
In that moment, 2 things are almost certainly true:
1. The bug is in your code. 2. You are too tired/stressed/overfocused to see it.
So when I find myself in this state, I instantly stop working and go for a walk (or go home when its late enough).
Then, when rested, I tackle the problem again. I will find my bug, or, for the very rare case, find a way to prove that it really is the environment my code runs in.
But most importantly, I will have a sharp tool for the job.
The mere observation of an uneven distribution is not enough evidence for a power imbalance. It could also just be caused by deviation of interests, which would be totally fine.
Power imbalances cannot be reliably detected from the outside, so I won't comment on the ruby conf case.
The state of a marriage is not set in stone. It is absolutely possible (and happens all the time) that a great marriage falls apart because one or both partners gradually stop giving attention to each other. The opposite may also be the case. A marriage that started off badly or took a big hit still can be amended.
It just doesn't happen automatically.
Marriage is mainly what both partners[1] make of it, und requires constant work and care. Of all the divorces I have seen in my environment, there was always at least one partner who wasn't willing to give his share of commitment.
Quote I heard somewhere:
After 65 years of marriage, an old couple was asked how they managed to stay together for so long. The woman thought for a few seconds, and then replied: "You know, we were born in a time where people used to repair things instead of throwing them away."
[1] This admittedly does mean that the fate of the marriage doesn't lie completely in the hands of one individual. You can't single-handedly make your marriage a good one. So maybe thats even the singlemost important trait to look for in a potential partner: Check for the ability to cooperate.
Round 10: After being knocked down twice and hardly beating the clock, Corrales turns the match, traps his opponent against the ropes and causes the referee to end the fight.
[1] http://en.wikipedia.org/wiki/Diego_Corrales_vs._Jose_Luis_Ca...
Apart from that, I wonder how the long-distance running speed of animals without rider is measured. Seems like an interesting endeavor, since animals will run long distances only if they have to, which I suppose won't happen often.
To support this proposal: When I first arrived here (from your homepage), I didn't notice anything about guidelines until I stumbled upon a comment which mentioned them. Then I eventually found them on the bottom of the page (which can be quite long), where I seldom look at.
An alternative would be to just give those worried ones a warm fuzzy feeling, without even informing the others. Or, if that doesn't suffice, just live with the fact that a few people won't go to the cinema for a month.
Of course, I don't know how many people were "worried" in this case. I hope there weren't to many of them, that would be a sign that my country is getting really paranoid.
I went to the cinema last sunday (for Batman), and they had signs all over the place saying something like "In reaction to repeated worried requests about security, we will not allow visitors to be costumed and may search bags."
I won't comment on the knee-jerk reactions of the customers. What more interesting to me is the decision made by the people in charge there, in reaction to those "worried customers". Was the cinema management panicking as well? Or were they just not courageous enough to stay calm and risk being deemed as "not doing something about it"?
[1] http://www.pnas.org/content/early/2012/01/02/1114999109
More entertaining version: http://www.npr.org/blogs/deceptivecadence/2012/01/02/1444828...
I guess you haven't completely decided how your pricing is going to be, so I understand why you haven't published it yet, but seriously, you have buzz now, and people may not register today because they are unsure about the implications of it. Do not let that happen - give them at least the information you just posted.
Edit: It doesn't have to be super-prominent, but so that the missing information won't be an obstacle to registration.
1. Looks fantastic!
2. Where's the pricing? Coming from the landing page, I could not find it. You should really make this easy to spot.
- The court has ruled that reselling doesn't violate copyright, but nothing prevents a software vendor from forbidding the reselling in it's license. The court didn't force vendors/service providers to permit reselling.
- The court has not demanded that vendors enable the reselling technically.
- The court has limited its ruling to computer programs, and excluded media like ebooks, video, music and the like.
So in effect, this will change: Software vendors will have to change their licenses to prevent reselling.
[1]: http://www.heise.de/newsticker/meldung/EuGH-Klares-Ja-zum-We...
That's true, but in no way is this invitation a binding contract.
It's a temporary bargain: The big player gets a cheap way to offer more functionality to his users, and the API-users profit from the big audience of the platform.
As soon as one player decides that the bargain isn't worth it anymore, the deal is off. It's no one's fault, just the nature of it.
In code, "int errorType = 1;" would be a badly chosen variable :)
The expressions "false positive" and "false negative" reveal more semantics than "type 1" and "type 2", and are therefore much easier to remember.
When I use this example to illustrate how an information that was once "clean" can become "dirty", they don't seem to understand. They act like that "incident" is soo far away, some sort of horror story(!) that has nothing to do with today. Everything will stay like it is now.
I guess the idea of something like 1933 happening again is so frightening or detached that they just dismiss it.
EDIT: I should add that people who actually lived in the time of Nazi-Germany might have a very different reaction to jgrahamc's argument. I made my observation above mainly with young people.
This is the most fundamental reason I have seen yet, reflected (often unconsciously) in our daily lives: We have curtains, we talk in private, we have secrets we only tell to those we trust, have company confidentials, discretion, spokesmen, and don't negotiate our salaries in public.
Why? Because we instinctively try to minimize those who might take advantage over us.
Knowledge can be exploited in so many ways that it is very hard to tell if a certain piece of information is harmless or not. If you're at the mercy of someone else, depending on him not to exploit his knowledge over you, you lose freedom.
Most people at least feel this and therefore - in their social interactions - act accordingly. Interestingly, as soon at no human face is involved, my observation is that these instincts break down. I believe that's the core issue today, where most information isn't collected by some creepy stalker, but by web services, governments and card readers. They seem so detached from a real (potentially threatening) person, that our deeply engrained secrecy patterns fail us.
Absolutely. But I would say that is a different debate. In my case, I don't want to specify the behavior, but only the form, which is the counterpart of a static type, but more flexible (e.g. {} is likened to any structure that behaves like a map - the class doesn't have to be exactly the same).
With my like-function, I don't have to spend too much time specifying what is expected, and I get a lot of bang for the buck.
I want to do just enough so the code stays comprehensible and thus manageable.
(fn parse-int [str] ...) needs no type or unit-test to be understood.
(fn parse-appointment [str] ...) is better understood when it has {:post [(like {:id (UUID.) :name "me" :date (java.util.Date .)} %)]}
And as soon as the function gets really smart, and it's smartness isn't revealed directly by the code, it would be time for either a good comment or a Unit Test (or make the code better so that it does, which is an often forgotten option).
The main disadvantage of dynamic typing for me is the lack of verifiable documentation about what data a function needs, and which data comes out of it. This becomes a problem when
a) the data is complex (e.g. dictionary of lists of items with certain properties)
b) I haven't looked at the function for a while.
In those cases, I find statically typed code easier to reason about.
On the other hand, it absolutely maddens me that static type systems force me to spell everything out, even where it's trivial. It slows me down, it bloats the code (especially when you have to create a new class for everything) - which again makes it harder to see the purpose of the code instantly.
That's why I decided to make my own little pragmatic experiment: In cases where complexity is expected (or experienced) - and only there- I use the Clojure pre- and post-conditions to check the shape of selected parameters and/or its return value. It looks like this:
(defn german-holidays
"Returns map of german holidays, in the year of d."
[d]
{:post [(like {(date 1 1 2012) :easter} %)]}
...)
(defn calendar [c start-date end-date]
{:pre [(like {:appointments {} :new (list)} c)]
:post [(like {(today) {:occupations [] :appointments
#{}}} %)]} ...)
You can instantly see how the data is supposed to look like, it will be checked automatically, and it is close to the actual code where you need it (unlike e.g. Unit Tests).I'm not yet sure how this experiment will fare in the future, so any suggestions or warnings are appreciated.
If the Pirate Party would form a coalition e.g. with the Union party, they would have to negotiate a coalition agreement. And each party will make sure that they please their clients (i.e. their voters or other supporters) sufficiently. So the Pirate Party would probably abandon their weaker positions (e.g. economic policy), but hold their ground on their main topics (copyright/patents etc.).
See this German link: http://www.heise.de/newsticker/meldung/Bundesregierung-sieht...
That's a recurring theme when management screws up badly.
Intellectual honesty applied to this particular situation:
1. The management should know that the engineers are more profound in the topic than they are.
2. The management should know that lives are at stake.
3. The management should notice that the engineers take their time and argue until late at night, mentioning "death", "explosion"
4. The management should know that communication skills may vary.
But management still did not act upon it, because they did not know their limits. That's their fault, nobody else's.
I'm glad you take your responsibility seriously.
This awareness should be exploited (in a good way) appropriately.
- We as those that do understand the issue have the responsibility to explain the problem to the majority. I still find it very difficult to effectively reason against censorship, privacy and the like to "normal" people, in words that they can relate to. A few weeks ago I personally accepted that challenge and are training. I thought this thread was a good inspiration: http://news.ycombinator.com/item?id=3425973
- Those who speak in public, especially in the mass-media, should not think that they can win a discussion only with arguments, no matter how valid they may be. Please ramp up the rhetoric skills. Alexis Ohanian does not look like he is an expert in PR, so maybe he should be joined by public speakers with experience with hostile (and outright lying) opponents, but he made a very good start, and makes notable progress each time I see him. I know I would be killed out there. Thanks Alexis, and keep it up!
I applaud the stand that Wikipedia makes and, being a german, propose that the blackout should not end on English Wikipedia. The USA still is the most influential country in the world, and this fight is international, just as the web is international. Please do not mourn for one day without your favorite sites. Show some solidarity among internet citizens.
I am quite happy with the progress that has been made.
1. Time. A discussion typically only lasts one day, and after that its mostly silent. Alongside my job, I simply can't find enough spare "thinking-time" to really write a thoughtful comment in that time frame. I feel that my comments would be more of a knee-jerk reaction than a real addition of value.
2. Language. My mother tongue ist german, not english. While I've been told that my english is quite reasonable, I still feel insecure in it, especially when I read incredibly well-spoken comments. And I do regularly make some mistakes, especially in grammar, and I don't like making mistakes in public (I guess nobody does). And of course, it takes longer to write a comment - see #1...
To me, that's a small sacrifice that can be really rewarding.
I strongly hope this will happen, especially for the sake of non-US countries like mine.
There are a lot of comments saying that the blackout should spare non-US countries as it does not affect us. For those who feel this way, please read holmesworcesters comment: http://news.ycombinator.com/item?id=3235431
Not only the USA is pressing hard to "control" the internet. Similar attempts will be made in the EU, in fact, one is already underway. See ACTA: http://en.wikipedia.org/wiki/Anti-Counterfeiting_Trade_Agree...
If Wikipedia and hopefully Google would really replace their site for one day, it would raise the peoples awareness to such issues dramatically. And if some American politicians lose their jobs over it, some European politicians will keep that in mind when the next "Anti-Internet-Law" (of course it would never be called that way) is proposed.