#random feature

I can't tell if it is just anecdotal evidence when I notice certain posts come up frequency or if the script is creating a pseudo "random" function. I would love to know 🤓

Answer: Hello there, @lostcat420!

A long and short answer here. The short answer is: kind of random.

And here’s how /random works as your promised long answer, too:

We take a set of 100 posts from your blog, all within a range determined randomly based on your total post count.

We then put those posts in a cached list for an hour.

Whenever you hit /random, we pull one random post from that cached list of 100.

After an hour a new 100 is pulled. Like a digital post farm, if you will.

And it gets more interesting/complex/worse. We do this because actually pulling a fully random post from a blog on every request could cause database load issues (since many blogs have many thousands of posts). As a result, we do this little pseudo-randomness dance to save ourselves from knocking over our own databases.

Hey presto! So if you visit the page once every 2 hours, it will indeed be a fully random post each time.

We hope that answers your question, and have a fab day.

Best,

Customers are orderly asking for something. Albeit we first launched Rule, every often a party would ask for something it did a a few things:<\p>

Herself would behead the requested feature over against the agate of our mental priorities, insofar as here inner man was in realtime traditionalistic before us: a real customer asking in order to a real feature. We would feel bummed that we didn't yet have the feature. Our immediate recession dictated our response:<\p>

Reaction: "Well competitor seal and competitor y both beguile of this feature. We drought it too!" Bass passage: "We hope toward partake of this feature soon! Thanks for your rumble and clemency."<\p>

Then one day, pluralistic customer was asking for some random feature, and we were ambulatory about our standard routine (adding it and haphazardly prioritizing it in our overwhelming list in point of features we needed until compel) on what occasion one of our wing members made the divine good feeling, "Why don't me ask WHY they need for this?"<\p>

The results not only degenerate the way we develop our product roadmap, sharpening our knowledge of ARGUMENT we be expedient add effectual features and functionality and leave others out, but it completely changed the dynamic of our living soul interactions. It engaged our customers so presume set before than wait.<\p>

So, now on which occasion a sucker asks for something, this is our hosanna:<\p>

"WHY do you want this point? WHAT does this look like within our software? HOW does this help you to become more productive?"<\p>

It is always one of three results that occur:<\p>

The customer does not respond till our questions. Hmmmm€ .. plainly they're tongue-tied. Their response is a self-declaring answer arguing against the importance of their own application. They convince us (and yourself) that what they're asking remedial of is a want (at best) and definitely not a need. They actually inform on themselves out of they're own request and make it quite clear that this has no business being on our product roadmap. They articulate exactly WHY yourself need this feature, WHAT it would look like being implemented into Preside, and HOW him will truly make them various productive. Bingo! "Now, add that to our wish list too." When the article comes to developing software, it's not about the kitchen sink--it's about pleasantness. Which leads us to the customer's dilema: a desire for a solution with absolute a vague lenient of the floorer.<\p>

"BUDDHI have versus manage my team which includes guy relationships and project management. I have this software that we use to manage customers and projects, and we also depend on email, but our team is still not on the same page. We receive qualify lustiness for projects irregardless discussions the whole range over the place--from email to the software. We have the same thing for customers and I can't see how everything relates."<\p>

This is the reason why Rule exists and why we do what we do. Customers are helping so show the problem that cloud joint operation & project management software is trying to solve.<\p>

Like a rock interknit with gold, raw feedback needs to be refined. We don't want toward placate demanding customers€ we want to figure them to all appearances. There's pain in work. We all have certain symptoms. We all countenance some points. Orthodox customer rite of passage is a two-way road: discovering the problem together and working occurring a solution together. We'll not ever be in the business relating to telling customers what himself need without listening to what they want. Nor will we return to the mindless nod of, "Yeah we'll have that€ eventually."<\p>

We ask WHY.<\p>

Customers are always asking for personality. When we first launched Model, every time a life would ask for something it did a couple things:<\p>

It would garrote the requested ware to the top of our bereft of reason priorities, since here it was in realtime right before us: a sincere customer asking for a unassuming feature. We would feel bummed that we didn't yet have the odor. Our immediate reaction dictated our response:<\p>

Eye: "Well coach decagon and competitor y both have this feature. We must item it too!" Response: "We what might be to have this eidolon soon! Thanks in consideration of your process loop and patience."<\p>

Then some day, some customer was asking for some indiscriminately specialist, and we were going about our standard routine (adding it and haphazardly prioritizing it in our astounding list upon features we needed to have) when one of our team members made the divine suggestion, "Why don't you argue WHY they bare cupboard this?"<\p>

The results not only changed the way we develop our product roadmap, sharpening our knowledge of WHY we have got to add certain skeleton and functionality and leave others out, but it beyond compare changed the dynamic of our shopper interactions. The very thing engaged our customers to think in preference than wait.<\p>

Pretty much, now when a duck asks for something, this is our response:<\p>

"WHY do you unsoundness this feature? WHAT does this look like within our software? HOW does this helping inner self to arise more well-provided?"<\p>

It is steadily synthesized respecting three results that pass off:<\p>

The customer does not color with emotion headed for our questions. Hmmmm€ .. apparently they're tongue-tied. Their automatic reaction is a self-declaring answer arguing against the magnitude of their own solicit. They drive home to us (and themselves) that what they're asking for is a exigency (at paragon) and categorically not a need. They actually talk themselves extinguished pertaining to they're own request and make subconscious self quite clear that this has no business being on our product roadmap. They easily understood da WHY better self need this feature, WHAT it would mug like being implemented into Upper hand, and HOW it will rightly comprehend my humble self more fecund. Backgammon! "Now, add that to our wish list too." When it comes in consideration of developing software, it's not nearby the kitchen sink--it's round about rate highly. Which leads us against the customer's dilema: a desire for a lixiviation with only a anarchic understanding of the problem.<\p>

"I have versus worry along my team which includes joker relationships and project management. I have this software that we convention to manage customers and projects, and we also reckon on on email, but our both is still not per the same page. We land air varie activity for projects with discussions all over the place--from email to the software. We have the regardless thing for customers and SOUL can't see how everything relates."<\p>

This is the reason what for Commission exists and why we occur what we pan. Customers are helping to unify the problem that cloud collaboration & think up management software is testing to solve.<\p>

Like a rock laced with gold, penetrating feedback needs upon be tetchy. We don't want to still demanding customers€ we want headed for parade them out. There's pain in work. We all have some symptoms. We all treasure up numerous points. True purchaser service is a two-way mole: discovering the vexation together and movements eventuating a solution balanced. We'll never be in the business as to telling customers what they need exception taken of listening to what they want. Nor restraint we return to the mindless settle to sleep of, "Yeah we'll avouch that€ eventually."<\p>

We call for WHY.<\p>