No affiliation but listened to a podcast by the founder a few days ago.
7,247 karma · joined March 25, 2008
I write at http://dangoldin.com.
I do a minimal amount of consulting on work with a focus on quantitative engineering, scaling systems, and architecture review. If you have an interesting project with some fun challanges definitely reach out!
Contact info: dangoldin gmail
No affiliation but listened to a podcast by the founder a few days ago.
We're looking for software engineers to come join us and improve the state of digital advertising. Our core product is a native advertising ad exchange that's running tens of thousands of auctions each second while having to deal with a variety of challenging performance and scale issues. The team is lean and likes to move quickly so if interested definitely reach out and let me know! dgoldin@triplelift.com
After reading this I may just bite the bullet and remove AMP and just cut out a bunch of crap to get it optimized for lower bandwidth devices.
Then it would be FROM X join Y on .. join Z on .. join (..) as T SELECT X.A, Y.B WHERE ..
I guess it's jarring but that's due to me not being used to it. Some people prefer doing joins using there where clause in which case the FROM ends up being in closer to location to the WHERE.
Are you guys familiar with it and I am understanding this properly?
Occasionally I'll find something useful. And sure I could have found it on my own if I was searching for that specific problem but occasionally something new comes across that piques my curiosity. Even then I end up looking at competing products (love relying on Google's autocomplete to do "product vs" and seeing what shows up).
The spam game is getting better and better too - I wonder what they're going to look like in a few years with some help from ML. At that point they will look personal.
I realize that they're likely automated but sometimes you just need to get me at the right moment in which I'm more likely to respond.
A shameless plug is I built a small visualization for the AWS detail log to help understand the cost drivers. All it is loading the data and visualizing it across a few dimensions but might come in handy for others - https://github.com/dangoldin/aws-billing-details-analysis
The good old days!
It's also the reason for trying to break down larger systems into smaller, elegant components.
It's in Python and a single file but it comes with a wonderful description and shows how a complicated task can be broken down into a few small and powerful functions.
We're looking to hire for a variety of roles ranging from fullstack engineer (PHP, Angular), to data engineer (Spark, Java) to a web server engineer (Lots of Java + Netty), to a data scientist (Spark + streaming), to an SRE, to a QA. We're exploring the idea of remote workers but are still figuring out how that would work but my initial gut is that we would want someone to be fairly experienced for us to go ahead with it.
A bit about the company: TripleLift is an adtech company specializing in native advertising. We're trying to get publishers to move away from the idea of commoditized banner ads so that they can focus on content first and monetization later. We do this by giving them the ability to drop a JS tag wherever they'd like an ad (typically in the main feed) and then rendering an ad that matches the look and feel of their site. There are quite a few technical challenges getting this to work at scale and I'd love to share more so please reach out - dgoldin@triplelift.com
As we shared earlier today, Instapaper is experiencing an extended outage. After 31 hours of downtime, we were able to rebuild a database instance to get Instapaper back online! In the interest of coming back up as soon as possible, this instance only has the last six weeks of articles. For now, anything you’ve saved since December 20, 2016 is accessible. We’re working on getting the rest of your articles restored, but wanted to give you access to your most recently saved articles in the meantime. Again, there hasn’t been any data loss. The full database exports are taking much longer than anticipated. We’re aiming to get the full archives available by next Friday, February 17 at the latest. We appreciate your patience and understanding in the interim. If you've got any questions or thoughts, just reply to this email or let us know at @InstapaperHelp on Twitter. - Instapaper Team
Not sure how it works on a production system.