6 ms·

This and the article about YouPorn's stack make me really want to go work for these places. I'm sure that the day to day challenges would be fascinating and it

by jetti 15y ago

This and the article about YouPorn's stack make me really want to go work for these places. I'm sure that the day to day challenges would be fascinating and it would be a thrilling technical experience.

dude_abides 15y ago
Yep! I wish it was more socially acceptable :)
- jetti 15y ago
  Seriously! I think it wouldn't be hard getting a job after wards, but the real challenge would be explaining it to the missus! :)
  - SystemOut 15y ago
    Pron doesn't have that much of a negative stigma attached to it when it comes to the tech industry. At least none that I've experienced. I do admit that I use the holding company's name on my resume/linked in profile but I always disclose pretty early on what it was just to make sure. If they have a problem with it I don't want work for them anyways. Also, you try to stop saying the word hard after working in the adult business....everyone snickers when they know where you've worked. ;-)
    - jetti 15y ago
      It isn't the tech industry's view I'd be worried about. It would just get tiresome having to explain that while I work at a porn site doesn't mean I watch porn all day when telling others what I do.
      - thret 15y ago
        I'd be worried about being the next Saeed Malekpour.
- rmc 15y ago
  Haters gonna hate. Ignore the people who tell you you're stupid. Us geeks have been picked on for years.
- igrekel 15y ago
  I know some companies build a separate IT entity to have a more socially acceptable front for their employees.
Killswitch 15y ago
I worked in porn running sites like these (Not in that scale, but hundreds of thousands of daily visitors) for about 10 years... Sure traffic is easy to come by, but making money is a lot harder. You have to sell memberships to porn sites that have premium memberships and you get either revenue sharing or a flat fee.
- Killswitch 15y ago
  Also you're fighting to sell a membership at sitea.com when some torrent or pirating site offers full rips of sitea.com within the top 10 results on Google for that search. So basically you're trying to sell a $5 cup of coffee to a guy while someone next to you is giving away that same coffee for free + a bagel.
  - jetti 15y ago
    Which is why I would want to work for one and not run one. I just focus on technical, they just give me my money and everybody is happy!
    - Killswitch 15y ago
      Unless you're targetting working for a major company (Brazzers who owns PornHub, Tube8, KeezMovies, Extremetube, etc) you've gotta have some serious skills, otherwise you have to create your own site... Not many in the realm of porn actually have full companies behind them, most of them are just your average joe running a site by himself. Not to mention most porn website owners are cheap... Doing any type of work in that realm is a pain.
      - jetti 15y ago
        Interesting. I guess the other factors come in and make the technical aspect less...appealing.
        Killswitch 15y ago
stickfigure 15y ago
Kink.com is almost always looking for talented developers. Message me (my username @ infohazard.org) and I'll put you in contact with the right people. It runs on a JBoss/Hibernate stack.
- va_coder 15y ago
  Masochism and Hibernate go together like peanut butter and jelly
  - stickfigure 15y ago
    Thanks to Hibernate's second level caching, Kink.com's entire user-facing website traffic could be served by a single appserver and single MySQL instance.* Try that with Ruby. * Not including NATS, which is an abomination.
    - jaggederest 15y ago
      Have done, thanks, varnish is the answer.
      - stickfigure 15y ago
        Unless you serve personalized pages. Which Kink does.
        moe 15y ago
        A small bit of javascript tends to help with that.
        stickfigure 15y ago
        That doesn't solve the problem at all, it just moves it from the generate-HTML request to a followon get-the-content-appropriate-to-this-user ajax request. Generating the information for each page is complicated, especially at Kink where your ability to interact with each "shoot" is determined by subscription rights, admin rights, microcurrency purchases, and who knows what else these days (I haven't seen the codebase in over four years). Hibernate's clustered 2nd-level cache is still pretty magical. It means that the vast majority of web page requests are serviced out of RAM with zero database hits - without writing any special caching code. And it's transactional. For a certain set of scaling problems, this feature is golden.

by jetti 15y ago

dude_abides 15y ago

Yep! I wish it was more socially acceptable :)

jetti 15y ago
Seriously! I think it wouldn't be hard getting a job after wards, but the real challenge would be explaining it to the missus! :)
- SystemOut 15y ago
  Pron doesn't have that much of a negative stigma attached to it when it comes to the tech industry. At least none that I've experienced. I do admit that I use the holding company's name on my resume/linked in profile but I always disclose pretty early on what it was just to make sure. If they have a problem with it I don't want work for them anyways. Also, you try to stop saying the word hard after working in the adult business....everyone snickers when they know where you've worked. ;-)
  - jetti 15y ago
    It isn't the tech industry's view I'd be worried about. It would just get tiresome having to explain that while I work at a porn site doesn't mean I watch porn all day when telling others what I do.
    - thret 15y ago
      I'd be worried about being the next Saeed Malekpour.
rmc 15y ago
Haters gonna hate. Ignore the people who tell you you're stupid. Us geeks have been picked on for years.
igrekel 15y ago
I know some companies build a separate IT entity to have a more socially acceptable front for their employees.

Killswitch 15y ago

I worked in porn running sites like these (Not in that scale, but hundreds of thousands of daily visitors) for about 10 years... Sure traffic is easy to come by, but making money is a lot harder. You have to sell memberships to porn sites that have premium memberships and you get either revenue sharing or a flat fee.

Killswitch 15y ago
Also you're fighting to sell a membership at sitea.com when some torrent or pirating site offers full rips of sitea.com within the top 10 results on Google for that search. So basically you're trying to sell a $5 cup of coffee to a guy while someone next to you is giving away that same coffee for free + a bagel.
- jetti 15y ago
  Which is why I would want to work for one and not run one. I just focus on technical, they just give me my money and everybody is happy!
  - Killswitch 15y ago
    Unless you're targetting working for a major company (Brazzers who owns PornHub, Tube8, KeezMovies, Extremetube, etc) you've gotta have some serious skills, otherwise you have to create your own site... Not many in the realm of porn actually have full companies behind them, most of them are just your average joe running a site by himself. Not to mention most porn website owners are cheap... Doing any type of work in that realm is a pain.
    - jetti 15y ago
      Interesting. I guess the other factors come in and make the technical aspect less...appealing.
      - Killswitch 15y ago

stickfigure 15y ago

Kink.com is almost always looking for talented developers. Message me (my username @ infohazard.org) and I'll put you in contact with the right people. It runs on a JBoss/Hibernate stack.

va_coder 15y ago
Masochism and Hibernate go together like peanut butter and jelly
- stickfigure 15y ago
  Thanks to Hibernate's second level caching, Kink.com's entire user-facing website traffic could be served by a single appserver and single MySQL instance.* Try that with Ruby. * Not including NATS, which is an abomination.
  - jaggederest 15y ago
    Have done, thanks, varnish is the answer.
    - stickfigure 15y ago
      Unless you serve personalized pages. Which Kink does.
      - moe 15y ago
        A small bit of javascript tends to help with that.
        stickfigure 15y ago
        That doesn't solve the problem at all, it just moves it from the generate-HTML request to a followon get-the-content-appropriate-to-this-user ajax request. Generating the information for each page is complicated, especially at Kink where your ability to interact with each "shoot" is determined by subscription rights, admin rights, microcurrency purchases, and who knows what else these days (I haven't seen the codebase in over four years). Hibernate's clustered 2nd-level cache is still pretty magical. It means that the vast majority of web page requests are serviced out of RAM with zero database hits - without writing any special caching code. And it's transactional. For a certain set of scaling problems, this feature is golden.