HN user

nickyp

58 karma
Posts0
Comments34
View on HN
No posts found.

Scribd | Software Engineers | Amsterdam, Netherlands | Full time | ONSITE or REMOTE (NL) Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, podcasts, and more. Our mission is to change how the world reads. In 2019 we hit 1M paying subscribers and have been growing since then. In 2020 we acquired SlideShare.

We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites. We have a very friendly, people-first, engineering-driven culture with competitive salary and great benefits. We are ambitious but at the same time value a good work life balance. To learn more, please check out https://tech.scribd.com.

The Service Foundations team is looking for:

- Ruby Software Engineer: help us define and evolve the next version of our Ruby/Rails foundations for services contributing to observability, logging, automated upgrades, RPC, event streaming and background processing solutions. https://jobs.lever.co/scribd/6179374e-abb9-4cf5-9c3c-b2af754...

- Go Software Engineer: we are writing more and more of our services in Go. We have interesting challenges in scaling services and building foundations. https://jobs.lever.co/scribd/96dca15a-1a0f-456e-b206-ba11775...

- SRE / Platform Engineer: take ownership of our infrastructure as code, work on logging, instrumentation, monitoring SLI/SLOs, and help us drive innovation and cost efficiencies within our global traffic routing layers (service mesh, CDN). https://jobs.lever.co/scribd/8e39d0ec-cfce-400c-a6a8-4612ef8...

The Content Delivery team is looking for:

- Site Reliability Engineer: take ownership of our infrastructure as code, work on logging, instrumentation, monitoring SLI/SLOs, and help us drive innovation and cost efficiencies of our content conversion pipelines. https://jobs.lever.co/scribd/7285115a-ed1c-40c0-95b2-ea0b1e8...

The SlideShare team is looking for:

- Senior Backend Software Engineer: after our acquisition, we have dramatically improved the product and plan to accelerate these initiatives in 2022. You will have broad ownership of technical direction. https://jobs.lever.co/scribd/17ccbd20-bbc1-4e59-a15c-a922923...

We have hired many people from these HN threads, including our VP of Infrastructure.

For more details reach out to me at nickyp at scribd.com.

Scribd | Software & SRE Engineers | Amsterdam | ONSITE

Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of last year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC '06), operating one of the largest Ruby on Rails sites.

In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity. We're also looking for a site reliability engineer to help us out in the cloud.

Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.

We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via: https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...

Scribd | Software Engineers | Amsterdam | ONSITE

Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of this year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC '06), operating one of the largest Ruby on Rails sites.

In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity.

We're also looking for a site reliability engineer to help us out in the cloud.

Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.

We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via: https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...

Scribd | Software Engineers | Amsterdam | ONSITE | VISA

Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of last year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites.

In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity.

We're also looking for a site reliability engineer to help us out in the cloud.

Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.

We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via: https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...

Scribd | Software Engineers | Amsterdam | ONSITE | VISA

Scribd is a reading subscription that gives you access to the best books, audiobooks, magazines, and more. Our mission is to change how the world reads. Beginning of this year we hit 1M paying subscribers (https://techcrunch.com/2019/01/28/scribd-1-million-subscribe...)! We are one of the oldest YC startups (YC ’06), operating one of the largest Ruby on Rails sites.

In Amsterdam we are hiring backend software engineers with solid experience in building, running and scaling out cloud-native microservices (preferably in Ruby and/or Go). We value a hacker mindset, clean coding and a natural aversion to complexity, or if you're a glass-half-empty person: an affinity for simplicity.

Scribd has a very friendly, engineering-driven company culture with competitive salary and great benefits. We are ambitious but at the same time we value a good work life balance.

We have hired many people from these threads. If you have questions you can reach out to me directly at nickyp at scribd.com (I'm the Engineering Manager of the Core Services team and happy to answer questions related to the role). Please apply directly via https://jobs.lever.co/scribd?lever-via=ze1h-jCbee&location=A...

Interesting observation.

I checked a couple of my 1Password files and you're right: usernames & passwords are encrypted, but not the website/URL they're associated with.

It's not 'compliancy' as much as they're reinventing the wheel.

REST was born out of a philosophy that the HTTP protocol already solved much of what you wanted to do. HTTP not only solved this, but solved this a long time ago and with 'great success' (aka The Interwebs ;-)

- Authentication mechanism

- Operations (CRUD) -> GET, PUT, POST, DELETE, ...

- Caching -> Use HTTP caching mechanisms...

- Resources -> URL's

- Formats -> mime-types + use a HTTP Accept: header

- ...

They reinvent the wheel on many of the bullet points above: custom operations, custom format handling, custom authentication mechanisms, ... That's why this really is one of the worst implementation of an 'RESTful' API

For those who want to take this kind of approach (object prevalence) in Common Lisp see http://common-lisp.net/project/cl-prevalence/

Sven Van Caekenberghe (the author of cl-prevalence) and I used this approach to power the back-end/cms of a concert hall back in 2003. A write-up of our experiences can be found at http://homepage.mac.com/svc/RebelWithACause/index.html

The combination of a long-running Lisp image with a remote REPL and the flexibility of the object prevalence made it a very enjoyable software development cycle. It's possibly even more applicable with the current memory prices.

I especially liked the fact that your mind never needs to step out of your object space. No fancy mapping or relationship tables, just query the objects and their relations directly. I guess that's what SmallTalk developers also like about their programming environment.

Learned that soon enough, only 2 Xserves were used and the rest of the rack quickly went back to Linux ;-) Although those puppies are still up-and-running of course (my Xserve adventure was in 2003)

I concur!

Ran a couple of Xserves a while ago to run web application stacks on it and most of the time I diverged from using the GUI to administer things I shot myself in the foot (Apache, firewalls, initscripts, networking etc.).

The nice hardware - those CPU load meters were gorgeous - unfortunately doesn't make up for those problems so I switched back to non Apple hardware + Linux and never looked back.

Don't fight the system is a nice mantra to follow when using Mac OS X Server and that's not hard when you use it to administer a collection of other Macs & the network they're on or when using the built-in services without wanting to tweak/upgrade the versions yourself (iCal server, Mail server etc.).

You're right, but I find that there are so many tap targets because of the table rows and cells that one double-tap zoom ('auto-zoom') is a hit-or-miss affair in mobile Safari . Even on the iPad, where the default font size is less of a problem.

HN _looks_ decent on mobile browsers, but doesn't handle all that well on them.

On iPhone: font sizes are really too small, voting arrows are practically not hittable without zooming in and trying to zoom in on the articles list confuses Safari (probably because of all the nested tables)

Excellent article & advice, especially for those who procrastinate all the time but don't even know it.

On the other hand: knowing that giving up in mid-flight has it own set of consequences will often lead to not starting at all

aka 'Go Directly To Jail, Do Not Pass Go' ;-)

The Logitech G13 game controller works flawlessly on Mac OS X and is a hell of a lot more comfortable if you want to game on your laptop. It can also store keymap profiles on the device itself so you can use it on any computer.

You're correct, that was the gist of it.

The main reason for building that mini reddit clone was that the Reddit developers had just switched to Python and to use something different than a mini blog platform for a screencast.

And of course back then there was no Twitter to make 'exciting' little examples to show of frameworks or libraries ;-)

It might be just me, but watching this felt like watching 'The Inconvenient Truth of the food industry'.

So all we need now is a meeting of the leaders of the world in Copenhagen to ignore this huge problem with the processed food everybody buys and consumes for at least another 20 years. (potential problem, if you're not convinced something is wrong with the massive amounts of sugar in our processed food)

[dead] 17 years ago

Agreed!

If it was 1997 I'd actually might read an article published on a CNET website, but it's not so I made this superfluous comment instead.

Basically: people who need to fill the slots to connect hardware that's as expensive as their computing platform and/or are running a software stack that can also cost as much as an iMac. In generally these people fit the 'Pro' suffix ;-)

High-end multi-channel audio interfaces and/or audio processing cards that accelerate audio plug-ins. Even Firewire or USB equipment works best if each device is using dedicated controller cards. (every Mac has only 1 USB/Firewire controller)

If you need to connect multiple 30inch Cinema Displays and still have proper performance (e.g. 3D) you need multiple GPU's. These cards often get replaced after a couple of years to boost performance.

And most often these kind of applications demand a lot of (very performant) storage so RAID controllers and lots and lots of hard-drives come into play.

If you're not buying a Mac Pro for these kind of workflows, you're just shopping for bragging rights I guess ;-)

And trust me: if you're using a Mac Pro in this manner you're not jealous about that very speedy iMac with that really nice display. It might me speedier, but it just can't do what your workstation was bought for.

And hey, maybe you'll buy one for the 'light web browsing' in your den ;-)

Hear, Hear! Also went to 20Gb (up from 8Gb) on the Mac Pro in the summer. Best 300$ I ever spent on hardware upgrades. Never close apps anymore, and never experience a swapstorm anymore.

Only one very, very big drawback: you'll want that much RAM in every system you use afterwards. I guarantee it: I just put back the screws on my laptop 10 minutes ago ;-)

Good point, but unfortunately that only applies to the performing arts.

And even then the issue of control comes to play. I know for a fact that if you want to play a certain big festival in my country you have to agree that t-shirts can only be bought at the designated stand, for a price that's higher than the price you decide and they take a cut of the profits.

Again, maximising profits by ripping of customers beyond your control...

Anyway, I wouldn't mind paying for a 3 hour live performance of Apocalypse Now (but only with the original actors, director and in the original location ;-)

Definitely contains interesting ideas.

But the problem with the lottery ticket mentality is that I think it mostly stems from the fact that the 'greedy and seedy suits' exert so much control over other peoples art on top of collecting all/most of the profits (even more so in the past).

Examples are ample: musicians not owning the actual music (in the past not even owning the actual recording masters), not able to decide how/when to (re)release albums, directors/creators of movies not owning 'video rights' and as such not in charge of how crappy a DVD is put together, comic book artists/writers not even having control over a character they invented from scratch...

The only reason you would ever put up with such ...ahem... 'fascism' is that you get compensated beyond a 'living wage'.

Also: I don't equate control/copyright over your own art/work with being able to control weather someone can get a hold of your art without paying for it.

That kind of thinking is completely obsolete this day and age and again only serves one purpose: maximize profits by ripping of (cfr. Nine In Nails album pricing in certain countries) or pestering consumers (cfr. DRM & unskippable 'do not steal' intros on DVD's you just bought)

Once the control problem goes away, new and equally profitable means of monetization can and should be created without feeling cheated (cfr. Radiohead In Rainbows)

We all know how it feels to work a job that has a crappy commute or crappy hours/people but happily put up with it if you're compensated more than enough.

When it comes to losing control over your art, only billions are 'more than enough' it seems ;-)