skysight-inc/HackerNews huggingface dataset:
This definitely isn't limited to PHP. While there may be instances where 'helpers.xyz' is OK, they're very, very few and far between. When you create a file like that, you've conceded defeat at actually naming things usefully.

If 'logging.php' or something similar doesn't fit what you're doing, and it doesn't fit well with anything else in your project, and there's no other way that would fit in with something intrinsic to your app, then this might be OK. But that's kind of hard to fathom.

In my opinion, though -- while I agree that it's something to be avoided at many costs -- the real problem with this, as with many things, is overuse. I'm on at least one project right now where the unconscionable overuse of helper functions (an entire directory of them with questionable file names, actually) has turned a Django project into horrible spaghetti code.

It's definitely not an isolated incident. In all languages, if what you're doing has any kind of logical structure, it's worth taking pains to make sure things go in logical places. You'll thank yourself in the future, and so will your successors.
I look forward to writing (essentially vim-) plugins for light table in javascript. Some day soon?

Extensions were mentioned on the blog about a year ago (http://www.chris-granger.com/2012/04/15/light-tables-numbers...), but as far as I can tell, they're still not here yet :(
I might not be in the same field as you but here are the 3 sites I've used in the last 8 years, I get 2-3 calls per day in the following days after posting my resume on these sites: monster, workopolis (I think this one is canadian not sure) & contract job hunter (cjhunter - 25$/y fee).

Make sure you use "high demand" keywords in your resume as robots are scanning these will pull it up for employers/recruiters.
Show HN: Spent. -- app that shows how much you spent on the app icon
Hi, I've been working on a simple spending tracker and my friend convinced me to release the MVP early to get some feedback.

I think it needs a lot more work like categorization and analytics to actually make it useful. I'm also not done with Android version either. What does HN think?
Mail me directly! We got a flood of people doing them, far more than we expected, and there have definitely been people falling through the cracks. Please feel free to bug us directly if that happens to you. We're trying our best and are happy to find ways to do better.
No way! The page works fine.

Copying and pasting whole articles into comments? Maybe when the internet actually breaks, do that. But when a couple of people have a whinge about a lightbox, or someone else complains about Flash which doesn't seem to be there...

What if they edit their article? Will you update your post with those corrections?
They've written in the past that the UI is essentially a webview, so I think that's a fair assessment

edit: also, I've successfully nuked the app at least once by evaluating document.write (or similar) in the IDE. heh
Stay away from rebase? What are you nuts?

What the hell is everyone doing working on master anyway?

Make your own working branch and merge it when it's ready. Don't mess with master if you're working with others.

If you are working on master (or merging to master, or doing something with master), merge and push right away, and if someone does something else upstream in-between, then rebase yours on top of it.

If you have local changes, and other people pushed changes to your upstream remote, first of all, you should have pulled before making changes (you know that's usually the reason) which would have done a nice fast-forward merge with no merge commit. If your commits are just local anyway, no one cares if you just rebase so it's cleaner! It's equivalent to having pulled first and then made changes. Exactly the same. No one wants to see an unnecessary merge commit anyway, that's just annoying.

All of this makes sense. Merge works, rebase works, sometimes they do the same thing, sometimes one's better, sometimes you should just not be dumb.

What's the problem? Geez, it's just git.
What? No. If Sally has already merged her commits into master, then those commits will never look like they've come from your branch.

If i'm misunderstanding this, then a worked example would be a really great way of clarifying it.
Or even less restrictive specifically for GPL apps...
People still use common lisp? ducks

In all seriousness, the plugin architecture will certainly allow for exactly that to happen. If you're interested in trying your hand at adding CL, I know a guy who could probably sneak you into the beta when it turns private ;)
Yes, agreed, if you are reading this book, don't skip the exercises! You might need to refresh some math skills (just a bit), but it is worth it.
I'd just like to note that that is not a particularly OO solution. You've essentially created a namespaced function. While this is still preferable to a bare function in a heterogenous helpers function file, it's certainly not a pure OO way of accomplishing the encapsulation of the InputSanitizer.
Implementing JS would be a huge undertaking (they'd have to implement lots of APIs and the DOM, for starters). Such text-mode browsers are usually light on resources, too, and this would change that. Also, JS is usually used with the assumption graphics support is there.
Alright, I emailed the address a few hours ago again, but I'll email you directly now, thanks.
I agree. I actually use trello more like a onenote replacement than anything else. An offline app would be really nice in a lot of ways. Unfortunately, there are still some places I go with my laptop that doesn't have wifi available.

Plus a standalone app would be nice too, having it as a separate application outside of my browser window, but I digress.
So, asking him to speak is sort of like inviting a subtle insult comic? :)

I can see a use for that. If you can get someone that has a true insight into your industry, and can combine that with the ability to subtly (or not subtly, whatever works) get you to reassess some of the less useful industry behavior, there can be a real benefit. A keynote speech at an industry event also becomes one of the best avenues for delivery.
Hard to tell until they release the source code (which is supposed to happen after the 0.4 release). The whole UI is actually rendered HTML using WebKit or a derivative for sure.
hmm… no mention of search/replace? Whatever, I'll try it anyway.
Isn't that just letting someone else write your helpers.php?
I am totally confused. Who uses an SMTP server written in PHP? mail() just writes a bit of stuff into a mail queue by default.
Happy to post a screenshot, but wonder if it is a violation of Google T&C?
> NEVER hash passwords with MD5/SHA-1/Hash-of-the-day

> PHPass will make life easy for yourself and keep your users' passwords secure.

MD5/3DES/SHA-1 are relatively broken. But saying "use this magical library" is really far from a solution. Who's to say that that library won't be broken tomorrow and then someone else won't write an article next week saying "don't use PHPass!"

Programmers just need to stay up-to-date with the latest trends and adjust their approaches accordingly.

> MD5/SHA-1/Hash-of-the-day is not, was not, and never will be acceptable.

MD5 was very much acceptable for the longest time. Back when everyone was using 3DES, MD5 was seen as the Bcrypt of the time. So saying that it "never was acceptable" is simply nonsense.

It was even what was implemented by the standard libraries and APIs of the time.
The official report says this was more of an excuse to get rid of old hardware.
Let me introduce you to my colleagues.

(who were a bit upset when they looked for jobs elsewhere)
> PHP version 5.5 (not yet released) will support Bcrypt natively via its password_hash() function. Use it.

This makes it sound like PHP didn't support bcrypt before 5.5. It did. PHP always has bcrypt support in 5.3 and 5.4. In older versions it also has bcrypt support if the operating system supports it.

PHP 5.5 only added a wrapper around the low-level crypt() API, which makes password hashes more convenient to use and less prone to error.
I have literally never heard of someone complaining that a person posted the text of an article to the comments due to a broken site.

Congratulations exodust, you're one of a kind.
The only way they never go outside of the author's personal computer is if the author squashes (or discards!) them before pushing. Otherwise, they will go outside of the author's personal computer.

However, they will never be a head outside of the author's personal computer, because they are pushed along with later commits that fix the brokenness. CI only ever builds heads, so the existence of the broken commits doesn't matter.
Even the "don't rebase once code is pushed to a shared repo" thing is more of a guideline than a hard and fast rule. For example you might reasonably want to clean up the history on branches that you have previously:

* Pushed to a distributed test system
* Pushed to a branch based code review tool (e.g. Opera Critic or Gerrit).

Using a heavily rebase-centric workflow for several years, with rebases on semi-public branches like those described above an expected part of the process, I don't think that history rewriting has ever caused me an actual problem. So my gut feeling is that people spend a lot of time trying to avoid something that sounds theoretically bad but isn't much of a problem in practice as long as some common sense is employed.
For areas such as Texas, New Mexico, Arizona, Florida, they happen very often during the summer. In Houston, last year we almost experienced load shedding (rolling blackouts) several times. ERCOT (the Texas ISO) forced large industrial customers to scale back demand to keep from imposing residential blackouts.

ERCOT sends out Emergency Response Service (ERS) notifications to QSEs (Qualified Service Entities) during these periods via a WS-Notification. The hedge fund predicts that during these events they can make several tens of thousands of dollars a minute with the diesel generators that they have deployed across the state. I think they believe that they can because they're having me write the code to start the units based on ERS notifications.
A friend of mine told me this longer ago than I care to be reminded of. "The older you are, the faster time goes. The telescoping effect can be quite startling."
I believe the requirement to maximize profit is a requirement of the stock exchanges, not a requirement of being a company.

A company can be created for many different purposes.
At Chicago in 1990, there were two intro classes; if you wanted to study CS (a math major at the time), you took 115/116, which were basically 6.001.
Can be put on someone's corporate card w/o budget approval. Dramatically cuts down red tape, so dramatically increases the number of corps that will readily sign up.
The H-1B work visa is fundamentally about cheap, de facto indentured labor.
While I greatly applaud the effort of implementing such a complex crypto scheme, I'm afraid I will have to wait years before using something like this. Who wants to be the early adopter of a cryptographic library?
it's not a course in programming. it's about problem solving and critical thinking. programming is just the means to achieve it.
If a 75% tax rate is being socialist big time, were the US communist back in the 50' ? Because they had tax rates up to 91% at the time. It's under 50% only since Reagan.

One source among others: http://www.beggarscanbechoosers.com/2011/09/america-prospere...
Text Opening Sequence with CSS Animations
If you know what you're doing you will not pass around huge arrays (in PHP) by value. Or pass them around (in CakePHP) at all, it's maybe a MVC warning flag that you do something in a place you shouldn't.

Related note: CakePHP 3.0 (current is 2.x) will use objects [1].

[1] https://groups.google.com/d/msg/cake-php/-TLn6RpHt4U/EAP0lt2...
It's simple: you're into working off of the newest state of the world as much as possible and I'm into working off of a snapshot of the world as much as possible and then merging in my snapshot plus modifications when I'm done. I think your way sounds like it deals with changes to the world more often than I want to, and also loses the context of what your commits looked like when you actually made them, but it's a fine way of doing things, and is especially useful if you're submitting changes to a project for somebody else to merge.
#1 actually no, a lot of designs have a spring pulling the rod into the core, and an electromagnet sticking to the rod, so if the plant utterly loses power the rod snaps back into the core and can't be pulled out. In theory you could attach the rods to bypass the safety feature but its just not happening.

Another issue is you run the coolant pumps to dump a couple MW into the system to reach operating temp/pressure after a day or so, THEN light off the reaction so you don't have varying steam conditions affecting the nuke physics. You don't "heat up" a nuke under nuke power as most assume. Its already thermally hot operating temp when you pull the rods.
Hours of operation alone isn't killing the USPS but it's a symptom of the larger, some would say terminal, disease.

Like most people who work in cubicles, I work 8-5. The nearest PO to my home is open M-F 8-4:30. The next closest is open M-F 8-5 and Saturday 9-12. That means I've got a single 3-hour window if I need to pick up a package or do something that requires human interaction. If I happen to be out of town or busy during that short window, I have to wait until the next weekend.

As has been discussed before, the majority of a bank's income is not on personal checking and savings accounts. For most larger banks, it's an ancillary service that they really don't try that hard to compete for most of the time. The real money is in business accounts and lines of credit (both personal and business). Even so, my local bank is open 10-7 every weekday as well as Saturday mornings and Sunday afternoons.

They've come a long way with online address forwarding, usps.com/redelivery, and other online features, but the window hours are terrible and it's endemic of the USPS' apathy with regard to customer service.
Not even a demo or a video, why is this better than any of the many free Google Reader replacements?
That was so annoying
No to which question? I think you meant "Yes"
This whole thing could be replaced with the far better http://www.phptherightway.com/
Actually we haven't implemented replace yet. There's a few things like that that will either end up in 0.4.* releases or 0.5 at the latest.
First set should be in your email shortly.
"[I] don't like being sold."

Are you serious? They are giving you a free and awesome product and you find it annoying that they earn money marketing to you personally? But not annoyed enough to completely stop using their products....
First, Kanban tends to be a small-group thing, even within large businesses. I'm sure someone in IBM is going to pay $200/year for a site license, but I doubt IBM is going to make a strong, centralized license control. Heck, it's not worth the TIME for a team to have the three meetings and twenty emails required, not for $200.

And really, why should they have a complex pricing model? It's not like Trello is expensive to develop/support/operate. If they can get 10k organizations to buy a $200 license, they make a cool $2M for a not-complex piece of software with a not-complex business model. That's a very high profit margin, and still cheap enough to repel price-based competition (even free).
I was just going to post that they are on my agenda. I have actually toyed with the thought of putting together a "book club" to go through them. I will probably have to put this off till the Fall, though.
The integration with Chrome is a nice way to get information about objects in JavaScript. Are you planning to similarly make run/debugging powered auto completion for python?
Just arrived, thank you!
ASP.Net CDN copies of jQuery are down
People set their PHP config to connect to a remote SMTP server rather than a local queue.

It isn't something you can control in the code.
Not terribly - you can get the same effect with `return Thing()'. This doesn't seem as useful as the similar bug/extension that allows pre-C11 scoped enums (see, e.g., http://stackoverflow.com/questions/441552/scope-resolution-o...).
I opened the page, closed it in anger and then noticed the text pasted here, which I read. It's worked out very well for me.
Hope everybody using it has a local fallback!
I wanted to suggest that, but I couldn't get it to work on my repo. Might be my version.
BlackBerry CEO Questions Future of Tablets
This topic is especially sensitive to me, so please enjoy the enraged rant below.

-----

I have a better proposal:

STOP DOMAIN ABUSE!

Remember, back in the day, when .net meant you were a network services provider, or when .org was only used by non-profit organizations. Wasn't that confusing as hell?

What the hell happened?

The network had a beautiful, well planned design, and PEOPLE LIKE YOU threw it away.

YOU ARE THE PROBLEM, NOT GOOGLE.

I recently had a conversation, with someone I respect greatly, about creating a series of informational sites very specific to US audiences, and he had a fit when I insisted on using the .us TLD. (Blasphemy, right?) He demanded I use .io, for a site that contained exclusively United States related information... Seriously?

I will not participate in this madness, and the HN audience should know better.

It's really simple, you see: your new project has lots of video content? Considering .TV? Is your company based in Tuvalu? THEN DON'T USE IT.

.AM? That's Armenia
.FM? Federated States of Micronesia
.ME? Montenegro.

The list goes on and on. Wikipedia has a complete list of them, along with their intended uses and common abuses. http://en.wikipedia.org/wiki/List_of_Internet_top-level_doma...

What makes this whole thing even more insane is that there are still tons of quality .us domain names, completely open for registration, and people insist on using TLDs of other random places! The Indian Ocean? Really?

I want some of whatever everyone is smoking.

"Only you can prevent domain abuse."
Twitter Ads now available to any user in the US for promoted accounts & tweets
You have a remote controlled robot, but not a single photo of this cool, unknown object?

Please tell me I missed something on that site.

On another note, this is pretty cool:

http://en.wikipedia.org/wiki/Jarosite#Use_in_materials_scien...

especially the bit about frustrated magnets. I wonder if the creators of these had any concept of this phenomenon.
$username = InputSanitizer::getInstance()->getPostData('username');

There. Now it's OO ;P.
The Makefile and pdf template for this and the redis book, I think are great, approachable, examples of using pandoc to generate a multi-format book.

Makefile: https://github.com/karlseguin/scaling-viki/blob/master/Makef...

template: https://github.com/karlseguin/scaling-viki/blob/master/commo...
Talk about some inefficient spending on Germany! Thousands of dollars wasted, and to think in the states we waste billions.
Paul Buchheit, creator of Gmail, tweets how "Bitcoin may be the TCP/IP of money"
Rebase is a powerful tool, and with great power comes great responsibility. It's easy to get stuff wrong with rebase, and it's also hard for most developers to get their heads around because it offers something that no other VCS does. I'm also very much reminded of http://tomayko.com/writings/the-thing-about-git, except to extend it even further, most VCS will tell you "you should have not committed broken code or written a bad message" or "you should have cleaned up your patch before committing it." Git, on the other hand, is extremely forgiving. I've lost count of the number of times I've gone off the rails and deleted a branch name or some other pointer to a commit in git, yet I could always pull it out (even if I had to resort to reflog). But enough about my shortcomings; why should you rebase?

I can think of two very good reasons to rebase: to cleanup a patchset before submitting it to a "central" repo, and to move your patch forward on top of another patch set (avoiding a merge). Often times, you might be working on something and get distracted, so you stash or commit and come back to it later. For whatever reason, you may have multiple commits that are conceptually related, but are separate. With git, it doesn't matter if these commits are one right after the other, or separated by other commits. You can rebase them into one commit that makes conceptual sense. If one commit reverts part (or all) of a previous commit, once you rebase and squash them together, the change and reversion cancel out so you don't get unnecessary twiddling of code in your commits.

The other time to rebase (that the article argues against doing all the time, which may have some merit), is when another repo you are pulling from has newer changes. So you've got your nifty new cleaned up commit, now you want to push it. But what's this? You can't push it because someone else beat you to it! No worries, you'll just merge. Hold on to that thought though: what's really happening here? Well, you want to put your changes on top of the changes from the repo you pulled from (and hopefully double check that they still build and the tests still finish successfully). Should this operation necessarily be called a "merge"? What if you just pretended that your commit had been based on the new stuff in the remote repo all along? That "pretending" can be accomplished with a rebase, and it also has the nice benefit of keeping your history clear of content-free "merging" messages.

So, when should you not use rebase? Never on a public repo that others have pulled from. Even if you are exposing your own repo as a master and warn people that things could change radically at any time, it's still probably best if you clone a personal/private repo off that, do your rebases there, then push clean commits to the public repo.
Tips & Tricks to Charge Smartphones and Tablets Faster
Furthermore, you can't point to a group consisting entirely of young people and just write off their behavior as "generational". A lot of youth behavior is simply driven by... youth. Youths are known to take greater risks even when fully informed of the potential consequences.
As long as it's easy to get photos into it, I imagine there's plenty of photographers who'll use multiple services.

Post it up when you're ready to launch, I'd be interested.
Which technology for realtime communication for a web application?
To Infinite Scroll or Not to Infinite Scroll: Where We’ve Come So Far
> 7. NEVER send emails directly from web page code
Sending emails is slow. Incredibly slow. Don't tie up a precious web front-end process with doing so. Use a message queue instead.

Well. MTAs are message queues. Why use a third party software speaking a third-party protocol, adding more complexity only to eventually be talking SMTP anyways. As such, my message queue is a locally installed MTA listening on port 587, talking SMTP.

This is as fast or faster than any message queuing system you can come up with, but as it's managed by the OS, it's bound to work much better than third-party solutions.

I also get a lot for free in exchange. Stuff like automatic resending, queueing, queue management and so on.

As such, I would not strictly agree with point 7 in the article. Sure - don't send mail by talking to a remote MTA, but if it's running inside of your local network, using any other queuing system provides nothing but overhead.

Furthermore:

>How do you set up Nginx so that it won't die or kill your server when you receive a big burst of traffic? You install it.

No. You are shifting the burden of correct app server configuration from apache to php-fpm or whatever other process manager you're using.

In the end it doesn't matter much whether you're down completely (misconfigured apache) or still somewhat capable of serving static files while unable to serve any dynamic pages (misconfigured php-fpm).