Live data from Hacker News

Thank HN: From Google form to $1k in revenue in one month

blog.oldgeekjobs.com

111–120 of 255 posts

Re: Thank HN: From Google form to $1k in revenue in one month

#111

Earlier quoted context omitted.

I've run into that as well. I'm amazed that popular ad blockers still do that, since it's obviously trivial to work around for actual ads, and will result in so many false positives.

They do it because it works.

That's a hilarious comment, and a good point. But you can tell when your ad blocker is messing with site functionality beyond just blocking ads (i.e., the false positives your parent comment mentions). And at a certain point, this is a differentiator among the ad blockers.

Re: Thank HN: From Google form to $1k in revenue in one month

#113

Earlier quoted context omitted.

Digital Ocean is just a simple VPS provider - I wouldn't even call it cloud. The usual cPanel PHP 5.4 shared hosting is consistently unreliable, insecure and a generally overall bad idea. Who would you actually even trust to run it?

> Who would you actually even trust to run it? Sysadmins. Scary scary sysadmins.

Your qualifier there made me laugh so hard because it's so true for all kinds of sysadmin-y reasons. Flashbacks of talking down a VP who said "just put it on DO or something" came to mind immediately.

Re: Thank HN: From Google form to $1k in revenue in one month

#114

I wish folks like Bray had championed this cause 20 years ago. It may not have done much, but... it feels a bit weird to hear old people complain about discriminatory impact. I can't say he was a contributing factor to the ongoing 'youth culture', but... it wasn't hard to see this coming. My situation may be somewhat unique, in that I've had grey hair since I was 18. Not a HUGE amount at 18, but... people noticed. By…

Stories like this worry me. I'm in my early-mid 30's and the grey is starting to become noticeable. If I was to go on a job hunt I might get it colored.

Re: Thank HN: From Google form to $1k in revenue in one month

#117
post #97

Earlier quoted context omitted.

> "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! If you're hiring someone 15+ years older than the rest of your team, there are going to be some cultural differences.

So? You're getting together to build things for money, not pounding back beers on the front porch and ranting about politics.

So you've never worked in a startup, then. :(

Re: Thank HN: From Google form to $1k in revenue in one month

#118
post #97

Earlier quoted context omitted.

> "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! If you're hiring someone 15+ years older than the rest of your team, there are going to be some cultural differences.

So? You're getting together to build things for money, not pounding back beers on the front porch and ranting about politics.

I think what the poster meant is that the twenty-somethings will just want to hack things up on the quick in Python or Rust while the old guy says whoa, let's sit down and write a specification first, and think about how we could architect this thing, and let's make OS packages out of all the components.

Re: Thank HN: From Google form to $1k in revenue in one month

#119
post #97

Here's the deal: Employers will exploit your age no matter how old you are. There is no "perfect age" for a developer. When you're young, they exploit you because you are inexperienced (especially at negotiation). When you are "old" they exploit by trying to play the age card. "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! So what is there? A ten year "ripe" age range w…

> "Not a cultural fit"--LOL--fix your stupid culture and stop exploiting people, you smug fools! If you're hiring someone 15+ years older than the rest of your team, there are going to be some cultural differences.

From my personal experience, this is utter bullcrap. At my first real programming job in a somewhat large company, we were an Android team of 6 developers aged 20-25 (the 25 y.o. guy was the team leader) and one dude aged 40. It was very easy to get along with him, even though we couldn't really relate to the problems of having a teenage daughter. I wouldn't call these cultural differences problematic at all - actually having an older person's perspective on your team can be quite beneficial, young people are often too impulsive for their own good.

Most of us were juniors facing our first professional coding gig. The older guy's experience was invaluable because he already knew a bunch of languages, had used lots of different SDKs and had made a ton of mistakes, so we could and did learn a lot from him. The only thing that struck me as silly was that he was a 'Junior Developer' by job title since he also wasn't experienced in the concrete platform, even though he could code circles around us newbies.

Re: Thank HN: From Google form to $1k in revenue in one month

#120
post #79
post #63

Earlier quoted context omitted.

Nice catch, never thought about it. Is it more problematic with preffixes (vs. suffixes etc.) or should we generally avoid any random string? Appending a hash to the script is very convenient to force the download of the new version of an asset (but maybe we have better solutions now, haven't considered this issue in a while).

In your site's code, reference the asset in a path that includes the timestamp the asset file last changed. e.g. /js/1476929634/myscript.js instead of /js/myscript.js Then use your webserver to rewrite /js/ /myscript.js to /js/myscript.js

Or just use a decimal hash, rather than hex? Eg in python3:

  import hashlib as h
  int(h.sha256(b" ").hexdigest(), 16)
> 24725091799402603688614593151141908335745916334489781770578761787218146381928

  h.sha256(b" ").hexdigest()
> 36a9e7f1c95b82ffb99743e0c5c4ce95d83c9a430aac59f84ef3cbfab6145068

It's longer, but even a 256-hash isn't that long? (and sha1 would probably be fine, obviously)

Post reply on HN