Founder of REVSYS (www.revsys.com) and former President of the Django Software Foundation.
Frequent speaker and author on tech subjects. Expert in building, scaling and maintaining complex web applications with Python, Django, React, PostgreSQL usually on Kubernetes.
What he means by "being dangerous" are things like os.remove(), os.removedirs(), os.chmod(), etc. He wasn't talking about crashing your own Python code, but being able to do dangerous things to the OS you're running it on.
That's actually a really good point. When I wrote that I was typically using single user Linux systems, but as a general tutorial this issue should at least be explained. I'll update it as soon as I can find a few spare moments. Thanks for thinking of that!
Braintree's API is a dream to work with compared to all of the other payment processors I've ever used. I try to steer all of our clients in that direction whenever possible.
I solve more problems taking a walk (to get coffee, fill my meter, or just walk) than staring at the screen for the same period of time. Often, walking around doing nothing, getting your mind off the problem is the answer.
Hence why you often hear great stories that start off "So I was in the shower yesterday..." and rarely hear great stories that start off "So I stayed at my desk for an additional two hours..."
I hate programming tests during job interviews, but you would IMMEDIATELY fail with me for using globals. There are VERY few things you could do in Python (or Django for that matter) that would be complete deal breaker for me, but you managed to find one.
In general yes, but with enough experience you start to just "know" where the bottlenecks are going to be. For example, if you know your user profile pages are going to be the most used, you focus more pre-optimization effort there rather than on some admin report that will be run monthly.
While it's still "pre-optimization" it's a smarter use of time to spend it where it will most likely matter.
These types of studies are flawed in that they assume the same technique works with different people in different situations. The best managers, bosses, founders, etc realize you have to treat different people and situations differently, it's constant adaptation to the situation at hand. Doing that is hard and more art than science.
Allow others users to rate reviews as helpful/not helpful like Amazon does. After a couple of unhelpful votes hide those from view by default. Not wonderful, but might cut it down some.
Simon, slightly better memory usage in most cases. More so if you don't end up stripping out all of the Apache modules you aren't using. But it's such a small differences it usually isn't worth changing from what you know and are comfortable with.
SSDs aren't going to help you compile faster anyway... Other than network I/O, disk I/O is the slowest operation on a computer, speeding that up does speed up most operations for most people. Everyone is I/O bound all of the time.
Doing TDD isn't always about having 100% test coverage and as you described is often wasted. But having coverage in line with how "important/complex" that piece of code is wonderful, frees you to refactor more easily and saves you from writing throw away test code, and/or manual testing.
Like most things in life, it's about moderation. Do you need 80+% test coverage on your "tweet this" feature? No. Do you need 90+% test coverage of your signup and ecommerce process flows? Absolutely!
Don't get hung up writing trivial tests as you described above, instead focus on the things that really matter.
Some college, didn't finish. Don't regret it really. Like certifications they only help getting your first couple of jobs in a field and often if that's a deal breaker for the company in question later on you probably don't want to work there anyway.
Agreed! Most of this advice isn't that useful and in all honesty can be bad advice for many sites. Really "fast websites" use external caching to not hit the database at all.
I switched from a 45-50 minute commute in bad traffic and tons of construction to a job with a <10 minute commute. Despite it being less pay and more hours I stayed for many many years. Those first few months after the switch were amazingly different. Now my commute is less than 5 minutes and I still want to move closer! I don't understand how people survive some of the punishing commutes I hear about. Life is to short to hate your job, it's also to short to hate getting to and from it!
Maybe email marketing isn't the right choice? I know personally I never purchase products emailed to me, if I spend 3 seconds scanning the email you're lucky. Granted I may not be your target audience.
You really want to begin any startup during an equinox. That's when you can stand an egg on it's end without falling over. It's a magical time! But seriously, what a silly thing to worry about. It's like asking, should I serve Coke or Pepsi at my startup? Which will make me more successful?
One of the best things, from my perspective is that it will give Kansas something that is positive for a change. There is lots of good tech here in Eastern Kansas, but all anyone knows is about our issues around teaching evolution and Fred Phelps. Sometimes makes it hard to convince a client on the coast that we really do know what we're talking about and aren't running a consultancy next to a barn.
Couldn't agree more on value vs time. It doesn't matter at all how long I slave over the hot laptop, it's the value I bring to the client! One hour of optimization that saves $5000 a year in server costs is a steal at $2000/hr over 2-3 years.
I have one single client who refuses to move off Joyent. My experience with them has been less than stellar. Frequent problems with no explanations, ask a support question like "How does one do X on your system?" and often get "oh you want to do Y I see, here is a link to the support forum for that." and the link isn't at all related to X or even the Y.
They aren't horrible, but I would never use or recommend them to anyone.
They might want to check the footer of djangoproject.com ahem. "Django is a registered trademark of the Django Software Foundation.", pretty sure this infringes.
I think we fit in the middle between the two. Obviously not necessarily local or exclusive, but mid to high grade content. I think the important part here is that most of the content will be a la carte and not leave media companies paying for a subscription that they don't or at least under use.