bennylope

The NYT at least lets you use PayPal. When I wanted to cancel I couldn't even get through to a rep, so I just switched my payment method to PayPal and then deauthorized the recurring payment from PayPal.

> If you are having trouble, get the SQL working first, and then figure out how to make your ORM generate that SQL.

This, specifically, is very good advice: using the ORM as a tool to implement a SQL-first solution. And not just good advice for beginners.

Maybe they're just deleting code in command mode...

It sounds like the "out-of-the-box" expectations created by the admin app are the problem. I mean, hey, Django makes exposing data models in the admin interface trivial! You can certainly create more complicated forms for relational data, but in those cases you can't rely on Django's default functionality to do as much for you. I've written or worked on more than a few serious apps including those with more complex user facing data and Django's worked beautifully. Happy to answer any specific questions you might have.

Make work programs cost a lot of money.

> My colleagues and I often discuss how we would've found it helpful if during our childhood we were taught pragmatic skills such as budgeting and resolving interpersonal conflicts—skills that we require on a day to day basis.

This is where many people undervalue the experience of having even a menial job at school age. I'm sure this school is amazing and this kind of experience at a younger age sounds great, but the best "real work" experience is "real work". That where you interact with strangers, adults often from different backgrounds than you, who aren't present because they're paid to watch for your interest, where you get a paycheck, and where you can be fired. I don't think that's an experience for which a school can provide an adequate substitute.

This should be retitled, "People Like Netflix’s Original Content More Than Its Other Sparse and Geographically Restricted Content"

That's what the "web" link below the article link is for.

I suspect we'll find that there's a difference between what was called shell shock (brain damage from blast waves) and PTSD (psychological trauma), and that it's possible to suffer from one or the other, or both.

This is largely true for someone who already knows the framework(s), probably less so when you're learning. There's less to do to make "a thing" that works in Flask than in Django. That said, many of the times I've reached for Flask I've realized, eh, it's going to be just as quick and "light" to do this in Django. At the working, production level, I wholly agree with you.

Sure, and none of that means that's his desk or his computer. Unless you have specific knowledge about what he keeps on his desk, this entire thread is a lot of silly speculation based on an unwarranted assumption.

How about this: Mark Zuckerberg poses for picture sitting next to [someone's MacBook] with covered camera and audio jack.

I wouldn't be too quick to say it's too expensive.

My set up is not dissimilar to your own. I'm comfortable working on the command line, using s3cmd to sync the site, modifying bucket policies, etc. Once you know those things - or if you enjoy learning them - it's all pretty trivial, but if you don't... well don't underestimate the hassle for someone who doesn't know this stuff. I'd think it a waste to pay $13/mo for what I'm happy to throw in an S3 bucket, but that's 3 venti lattes for someone not to have to deal with any of it. It's not the file storage they're charging for.

I've used both as well and this perfectly crystallizes my thoughts on them. Integrating custom models felt a bit more cumbersome in Wagtail but I've mostly chalked that up to my own experience gap between the two CMSs.

And for those companies providing services (i.e. people doing work, rather than just SaaS) there's a lot of subcontracting that doesn't show up in this data.

You really have to have a groomed database to get reasonably accurate data. At a former employer (federal market research) we maintained a separate database of contractors mapping the relationship between companies based on DUNS number, which enabled rolling up totals for subsidiaries. Of course that doesn't account for JVs or subcontracting.

Conflating one spectacular success with all [Harvard] dropouts is a silly comparison.

libsass is - understandably - a few versions behind the Ruby implementation. Most of the project teams I've been on working with Sass have opted for the Ruby implementation as a consequence.

Well I'm sorry, but that sounds altogether far too sensible.

> Together, these two factors have led to large amounts of research into sewage treatment, new technologies, and upgrades nationwide. Just because you apparently are ignorant of them doesn't mean they haven't been occurring.

While admittedly ignorant of the specific changes in water and sewage provision, I never suggested they weren't occurring - I said the experience for an end user hasn't really changed much. Even if the water quality has increased tenfold and a city's demand trebled in a decade, we're still pulling water from the tap the same way we were before, and our usage year over year doesn't change that much (on a household basis). My household needs and expectations for water service don't seem any different than 15 years ago, whereas my household needs and expectations for internet service are radically different. Governments do 'big' better than 'fast'.

> municipalities generally run water and sewage services without complaints

I'd largely agree with this from my own experience. The caveat here in comparing water & sewage to internet service is that water and sewage service - at least what we experience as end users - hasn't changed much over the years. Municipal governments are good at managing that type of service. I'm happy with the same water and sewage service that I had 15 years ago. Not sure I'd like the same Internet service. And I'm not so sure I'd trust my city to keep such a service up to date.

Python's [list] comprehension syntax was directly inspired by Haskell's list comprehension syntax. And it's also widely (I'd argue) considered to be the Pythonic way of composing lists (and other iterables), rather than using map. It's provenance doesn't detract from that.

And if you asked them, "Hey guys, raise your hand if you use the web" you'd get men and women raising their hands. "the guys" != "guys" in this case. The word is very - or awfully, depending on your point of view - ambiguous, and can be used in a gender neutral/ambiguous way, like third-person plural pronouns in other languages.

Not sure what's so ironic about this. That's the Mercurial server that's not responding.

It's more popular in certain geographic and industry pockets. I used to see long lines at the Pentagon and Crystal City for slug riders every afternoon/evening.

You might like this post and repo on the iterated prisoner's dilemma then: http://jacquesfuentes.com/essays/2014/10/31/Iterated-Prisone...

Would love to hear how you like it, as well as what you previously were using (or would be using instead).

>If you want to do open-source work on an area related to your job you must talk to your employer first

It isn't the law, but a some employment agreements give de factor ownership of any intellectual property an employee produces to the company, own time or not.

Not sure what an old lady renting a building has to do with the CBO, but I suspect that cmelbye is pointing out not that the CBO is efficient at its job, but that institutionalizing impact measurement (CBO) is insufficient in the face of powerful political incentives. That's how I read it, anyhow.

In addition to the previous answers, consider using hstore for custom variables. I've found it helpful for things like settings on customer accounts where these might differ quite a bit between accounts and change quite a bit over time. Otherwise the table layout applies to all accounts.

If you really need to separate data by customer then consider using PostgreSQL schemas. But I'd steer away from any solution that involves adding and dropping columns for different customers.