I ride the metro for about 1:30 a day (part of which is walking to and fro), which I prefer to my prior driving commute of 25-30 minutes. I have had to increase my fantasy and sci-fi novel budget, however.
One can perhaps take comfort in the fact that a civilization advanced enough to be aware of us would likely be aware of the fact that we were more advanced than what they could see at any given moment (or they had found a way to narrow the perception lag).
They would likely have extrapolated the savagery they saw and realized that we may pose some problems for the galactic community. RKKVs are probably on their way towards Earth as we speak.
I was in the Azure TAP program many years ago and they talked about this extensively to the participants. I would echo the consistency of direction on this. I had a vague sense that it was an attempt to quell enterprise fears about the cloud and lock-in, but perhaps not.
I'm not sure I quite expected to see this on HN, though I'm glad it was posted since I happen to be trying to learn novel writing. I thought the before and after example of the basketball article was a concise and clear way to explain over-writing. The second version was clearer, more accessible, less obnoxious and no less informative and narrative. A series of poetry and short fiction teachers in college helped me become self-aware about this bad habit. I still make the mistake consistently, but I have learned to either catch it or agree with the suggestions of my peers who catch it when I don't.
I personally believe that programmers can learn from poets, for example. Write constantly. Read the work of others, both critically and for enjoyment. Writing is the sexy part, but revising is at least as important a task.
I find your last sentence amusing because I actually prefer editing to writing. It's when I'm editing that I feel like I'm actually applying a craft. I get the same kind of satisfaction from editing my words that I do from refactoring my code. In both cases, it is often only after doing the initial work that I realize how it should be structured, and reworking it into that elegant structure is satisfying.
Can't agree with you more, both for refactoring code and editing prose.
I find it also sometimes helps to perform the revisions while in a somewhat altered state of mind (be it mood, setting, music, minor inebriation, or otherwise). It helps you look at the first draft with fresh eyes and see better ways of structuring things and removing excess. Make a version with your prospective changes, then compare the before and after copies a day or two later (this time sober if you weren't before...).
I never thought to compare writing words and writing code, but it's true. The writing phase is simply getting all the ideas out, and the editing phase is to make... beauty out of chaos!
I am the same way. I found it surprising. I get so much positive feedback from the editing process that I have actually developed a routine of editing as I draft. Although it improves the quality of my draft, it takes ages. For poetry, it worked well. For novels, I think I'll need to break the habit.
Though for what it's worth, I've seen a lot of professional authors that warn about that as another kind of trap that beginners fall into. That is, paying too much attention to the revision process, at the expense of producing actual finished works.
I think it belongs - What he is suggesting carries over to technical endeavours as well.
1. Learning to cut mercilessly improved clarity of my emails and documentation.
2. Learning to put my head down and carry on till a project is first draft complete, warts and all improved my ability to actually _complete_ things.
3. Peer review as a bullshit detector is good.
I'll take Poe or Lovecraft over King any day for entertainment, but I might just crack 'on writing' after reading this article. The man sounds pretty dialed in.
I was at a product management event once and met a guy who managed a product in this space. A group of us went out for drinks after the event and he ended up explaining what he did. At some point he mentioned "Chinese hackers." Another guy in the group called him on it, wondering why he just assumed it was Chinese. He laughed and said that the near constant level of activity they see goes basically flat on Chinese New Year.
I suppose if you're not a Chinese hacker, it might pay to pretend you are by tailoring your working hours and days.
I read it the way you apparently intended to write it. In college, getting to where I could write and get published poems that weren't a personal embarrassment took more or less the same amount of study and practice as getting my CS degree. I think mastering either craft would be a comparable endeavor and accomplishment (though one would pay much better).
The nice thing about compilers is they tell you when your code has a problem. There's no equivalent barrier to posting awful poetry-drivel on Facebook ;-)
My experience has also been that managers at the "average company" these days are pretty much expected to both manage and be a fully productive individual contributor. Realistically, this means that they spend about 80% of their time working to hit their own goals, which directly point at them, and 20% of their time (at best) really working to enable their team to succeed, which can always be deflected from direct responsibility to some degree. Since most managers' managers are also in the same boat, they can't tell when someone is shooting their own team members for self-preservation because they are too busy to have any sense for the morale and culture they've created.
In my personal opinion, you get a healthier culture if you either 1) have managers and let them manage or 2) admit that you require them to be individual contributors and restrict their "managing" purely to part time HR initiatives and not to actual additive management (something more like extra-curricular mentoring and not talent management, career and skills development).
I should caveat that I've had good managers, bad managers and completely mediocre managers. So I do believe that, although rare, it can be done well and it can provide value to individual contributors' careers and to the company's value. I just don't assume it's automatically the right approach at every company.
Lawrence and crew just responded to my tweet on this. They use Stripe, which is encrypted. The SSL certs for the page that is unencrypted will be up later today.
I'm very unhappy with their replies on Twitter. They can't just say that the information is going to Stripe and Stripe is safe.
The facts are, they have a form which asks people to put their credit card number in it. That form is on an unprotected page, which means it is vulnerable to some advanced attacks even before posting.
Further, the form posts back to the same unprotected page. I don't see any evidence of fancy Javascript behaviors to prevent the posting, but even if it were so, they are still putting their users in significant danger of having that information plucked out of the air by anyone who might be able to sniff the traffic on any leg of the trip from the user's Wifi all the way to the company's firewall.
The HTML of the form shows as POSTing to the same page, but the Stripe JS captures the submit event and cancels it, then makes an API call to Stripe's server via a secure connection. It works, but it is still somewhat vulnerable to MitM attacks.
I like @lessig's latest response. Much more firm and reassuring:
I'm pushing and anxious because this is exactly the sort of problem that could negatively impact the entire campaign, and I think there is worth to the goal. I hope they take a strong stance and fix it quickly rather than trying to placate and coast to a fix.
Looks like they got the cert deployed, although the process isn't directed to https yet. I hand-added https to the URL for the payment collection page and had no issues.
I've spent a lot of time in technology product management (PM) and I still frequently encounter "Product Managers" who are doing entirely project management (PMO). And there's business analysts and other technical product management functions that are centered around requirements and specifications rather than market discovery, product fit and strategy, plan for making actual money, etc.
I'm not suggesting that anyone in the thread is conflating PM and PMO in this way, but it's a challenge for the profession and I wouldn't be surprised if given posters perspectives reflect different views on what the PM role is actually supposed to be the expert on. I don't think it's their fault. We use a hyper-generic name that is almost indistinguishable in full and acronym'd form. We also tend to write awful job postings, though that's a rant for another thread.
Well, the PM job is so fluid depending on the product, the team, and what's needed to get it shipped. I've worked with engineering teams that just needed project management from me, although I think PM-style project management may involve more ruthless decision making as it's usually a case of fitting a very large peg into a very small hole.
Re: #16, my experience with and in management positions is that we no longer think of managers as people who specialize in management and whose function is to help a pool of natural talent stay coordinated, focused, challenged and rewarded. We instead think of them as people who do 40+ hours a week of their own specialized, non-management work but who also have to do performance reviews. I try to take a mentor/servant/counselor approach with my team, but it's difficult to do and my own experience suggests that it's a fairly uncommon mentality.
