2,185 karma · joined September 27, 2010
Let's say you are trying to "synchronize" a secondary data store with a primary data store. Changes in the primary data store are very "bursty", one row will not change for days, then it'll change 300 times in a minute. You are willing to trade a bit of latency (say 10 seconds) to reduce total message throughput. You don't care about capturing every change to the primary, you just want to keep it within 10 seconds.
It feels like there should be a clever way to "debounce" an update when another update overrides it 500ms later. I know debounce from the world of front-end UI where you wait a little when doing autocomplete search based on keyboard input so as not to overwhelm the search.
> Traditional advertising could never get your attention.
Are you serious?
> Before social media advertising would have to hitch a ride with some content produced for something else.
This is exactly what social media advertising does.
>Billboards, newspapers, television shows, and magazines all tried to provide a use value to their customers and audiences
What does that even mean?
Advertising was effectively getting attention and subverting behavior long before the internet. Watch the Century of the Self for some prime examples.
If you set an advertising campaign that specific, you're going to get no impressions. Researchers keep using these examples of "disturbing levels of specificity" of Facebook targeting. No advertisers actually do this. They're too lazy and they want volume. They do plenty of other disturbing things but this is not one of them.
It seems like the important word in the legalese you posted above is "non-exclusive."
Say a user wrote a review on TrustPilot, and copy/pasted it to an email to the business. Then the business posted the review from the email on their website. Are they now violating TrustPilot's TOS?
Over the past few years, Prisma has been quietly building a complete zero to advanced guide to databases that I've started to refer people to and use as reference myself. It stands out to me because it is focusing on a broader topic than what you typically find in docs, it's written simply, it is super comprehensive, and it's not trying to sell something.
It seems like more of a threat stance to various partners and ecosystem players than anything else.
You can trace a constantly evolving visual style in web design back to a root cause: "The need to look modern and legitimate."
It's hard to remember, but there was once a time where good stock photography was a way to look modern and legitimate. That birthed a thousand cheap stock photo sites and eroded the effect.
So we moved on to a constantly evolving style of illustration. Skeuomorphism, corporate memphis, gradient meshes, clay. Websites use these to signal modernity and legitimacy, but the very use of it erodes the effect and they have to move on.
If we can write an ALT tag and get a professional-looking illustration in any style, that will erode the effect, and we will have to find new ways of looking modern and legitimate.
Maybe that will involve professional illustrators, or maybe it will move somewhere else, just like when it shifted from photogs to illustrators.
For something like consulting, the author's proposal sounds like an overcomplicated "pay for performance" model.
For example: Advertising agencies get paid based on the conversions they drive, law firms get a cut of winnings, whistleblowers get a percentage of fine, recruiters get a fee based on placement, etc...
Doesn't GitHub cache every image in their own CDN for security and control purposes?
Is it just a matter of setting headers?
The share of discourse on HN about PostgreSQL, SQL, and Databases is growing noticeably. [0] I, for one, hope we are seeing the pendulum swing back from code-centric architectures and NoSQL to a new golden age of data-centric architectures.
Next you need push and pub/sub semantics in PostgreSQL so you can build something like this [1]
[0] https://toddwschneider.com/dashboards/hacker-news-trends/?q=... [1] https://tonsky.me/blog/the-web-after-tomorrow/
>4. Database queries can probably be left uncached
...but maybe I am thinking about it wrong. Imagine building Quora as a Rails App. For all the interesting user stats like "your answers have been viewed 28,000 times" I feel like your choice is to either denormalize in the application logic and database or cache the complex queries. Are most people taking the first approach?
If you hope to get customers - You're thinking about it wrong. First, the typical buyer doesn't trawl a "SaaS Apps" list site looking for services they need. Second, even when you list on a site like Product Hunt, the chances are low that any given visitor that sees your site the day it's promoted also needs your service. Instead, think about what search terms someone might use on Google when they have (or are about to have) the problem your SaaS app solves. Try and write the best answer on the web for those searches.
If you hope to get feedback - Again, probably thinking about it wrong. I'd try finding people who A.) You don't know and B.) Are uniquely qualified to give feedback on your service, and get in touch with them, try and offer something of value to them in exchange for feedback.
She was in the hospital for something different at the time so doctors were able to watch it closely. It looked really bad: blackish grey and stiff like she had gotten frostbite.
The hand specialists warned us that amputation might be necessary if it gets infected, but said ideally they just "wait and see."
Sure enough, three weeks later they were able to literally just pull off the dead part and find a new thumb growing underneath!
Here are before and after photos: https://imgur.com/a/S8hlhKz WARNING: GRAPHIC
We're hiring at all levels of engineering positions (eng. manager, engineers from new grad to principal), technical writers, developer advocates, and more across product and marketing - for the full list, see https://materialize.com/careers
WHAT: Materialize is a streaming database for real-time applications. We are focused on bottom-up developer adoption, our core software is written in Rust, free to use and source available, our business model is a cloud product built with Python and Typescript that handles management of Materialize and lets businesses focus on building value.
WHO: We are a team of 40 experienced individuals in databases and distributed systems, and looking to add more folks with that interest and/or experience to our team. Our cofounder and chief scientist is Frank McSherry, the primary author of Timely Dataflow (http://timelydataflow.com) and Differential Dataflow (http://differentialdataflow.com), the two open source projects that power Materialize.
WHERE: Primarily based in New York City but also open to remote positions in the EU and NA.
Kafdrop is great, especially if you're already running everything else in Docker, just add a few lines to your docker-compose and get a free web UI for troubleshooting/introspecting.
Maybe there's a brief moment of "I'm impressed with how much work you put into this" but for that to happen, you kind of have to see the work being done.
I think that's why impressionism has such staying power, impressionists realized that your brain doesn't need photorealism. They were panned by their contemporaries who were focused on photorealism, but time has proven they were onto something.
Even now the impressionist-style neural nets don't get it right.
BTW you have a typo on the homepage. CTRL-F for "slinghow"
I worked in Marketing and community at DigitalOcean over five years as it scaled. I had contributed to a hodge-podge of overlapping analytics tools running in managed chaos at my company, I had watched another team get hoodwinked into a multi-year deal with a big analytics/testing tool that had been in development for months without yielding a single test, I had seen people throughout the company struggle to find answers to basic analytics questions due to the complexity of the tool stack.
I got a Volument pilot going on the public part of our site, and while the scale really strained the Volument infrastructure, I absolutely loved the opinionated and simple interface.
It was like what Netlify did for static-site hosting, applied to analytics. Volument took the 3000 views and features of a legacy provider like GA and just figured out what people actually need and boiled it down to 5.
I've changed companies since, but am excited to test this new version at my current company. The people at Volument are super-great and responsive, and if the new one is anything like the original it's going to be very useful.
[1] https://volument.com/blog/minimalism-the-most-undervalued-de... [2] https://news.ycombinator.com/item?id=21871491
1. Universally Negative - Either it's cryptocurrency-related, or it depends on source of negativity:
A. "I read the site and I don't know what this is" - Genuinely bad explanation of an idea that doesn't seem particularly technically interesting or challenging.
B. Criticism of superficial aspects (e.g. website, related topics) - Genuinely bad explanation of an idea that DOES seem particularly technically interesting or challenging. _(Commenters don't get the message, but are worried they'll appear ignorant if they say it.)_
C. "Nobody needs this" "Why is this a thing" - Either bad or HN is nowhere near the target audience.
D. "This is not the right way to do it" "You can just do X" - Either bad or revolutionary (and new enough that the idea hasn't clicked with anyone.)
2. Polarization - A. If positive people are REALLY positive about it - potentially a disruptive technology, potentially ahead of its time.
B. If negative people say it's actually much harder to solve - the idea is great in principle but the only reason it hasn't already been solved is it's not possible or very difficult in practice.
3. Universal Adulation - It will transparently never make any money, it is some kind of attempt at decentralization that will never get adoption beyond hardcore nerds.They treat articles like code, the average article has 30+ edits, and reports of issues are triaged and turned into edits and updates.