Frequently used in a sentence

Frequently in a sentence as an adverb

There are frequently inane comments of this type at the bottom of HN threads. What's alarming is to see them at the top.

Something that happens quite frequently is non-technical friends see my laptop at night and ask "why it is orange?" .

I like to share advice on language learning, because this topic comes up on Hacker News frequently. I hope the FAQ information below helps hackers achieve their dreams.

The Next Web is featured on HN quite frequently, so it is logical that any criticism of your website would feature here as well. And I wouldn't call it crawling, you've got top billing.

Unfortunately, if you take it frequently enough, it becomes habit. It becomes second nature.

The lack of shading and UI chrome also means that UIs frequently become jumbled. Sections of UI blur together where on any other platform they would've been separated by a visual line, shading, or something else.

Employers frequently advertise for highly specific skill sets that almost nobody has. Then when nobody or only fraudulent people apply, they reject them all and claim a skills shortage.

But, it's not very frequently reported in mainstream media. I only know about it because I know some of the people involved and follow activist-oriented news sources.

****, they'd even break documented APIs frequently. Even "breaking" API changes only get 30 days warning, and that 30 day minimum window was set in 2011 after developer complaints!

Shuttleworth's well-articulated comment and decision to close bug #1 show the kind of open-minded, flexible thinking I wish I would see more frequently from other project leaders in the free/open source ecosystem. The decision to close the bug reminds me of a quote attributed to John Maynard Keynes.

In fact, as was pointed out by a kind reply to that comment, I have prepared this FAQ document in advance, because questions about company hiring procedures frequently come up on Hacker News. I began summarizing the research about six months ago, and other participants here on HN have helped me take this FAQ through several revisions as it reached its current form about two months ago.

I learned how to architect systems for scale, and a lot of practices used for robust, high-availability, frequently-deployed systems. I learned the value of research and of spending a lot of time on a single important problem: many startups take a scattershot approach, trying one weekend hackathon after another and finding nobody wants any of them, while oftentimes there are opportunities that nobody has solved because nobody wants to put in the work.