We just started using Asana a couple of months ago, but we're not seeing the performance issues some other folks are mentioning. I just hit Asana full refresh and it took 2-3 seconds to render all of the components in My Tasks. It seems pretty snappy in my opinion. Asana with a few Zaps has been great. Because I know they're watching...could you guys add a calendar view to the iOS app? =)
I own a coffee shop in addition to my tech work. Most people know having runway is important to any startup. If he had to declare bankruptcy 6 months after opening he wasn't set up for success.
If you make good coffee, choose the right location, and do a decent job of marketing you can get cash flow positive with time. Acquiring customers can be slow, but once they taste good coffee they will come back.
Much of the other comments here are true, you don't open a coffeeshop to get rich. The only way you can make good money is to scale into multiple locations.
This decision is getting a lot of hate here in Alabama and I'm surprised to see some support here. The knee jerk reaction is to think this a separation issue, but its really not. States can delegate authority for law enforcement to anyone they choose.
With that being said, its still a dumb idea. Our government is wasting time debating this issue when there are so many topics that are real issues. This church could hire full time security people or outsource to a security company. My alma mater had a university police force, but decided to contract the local police instead because it was more cost efficient.
And Christ never said life was going to be safe. He actually said the opposite.
Livelihood encompasses more than just financial. If it were just money most people could get by. The stress on a person and their family while job hunting, especially at the CTO level, can be pretty huge. I would much rather have some runway to find the gig I want rather worry about my reputation.
If you really need the unemployment I would blow the whistle. Your livelihood is always more valuable than a reputation. I doubt your reputation will take a huge hit for reporting what sounds like a dishonest company.
I don't want to get into a my framework is better than your framework fight, but I disagree with people who say flask can only be used for simple applications. Just because it's a micro framework doesn't mean it's only for micro apps. The trade off on framework size is how much functionality you want out of the box. If you want a bunch of features and are okay with doing it the Django way, Django is great. If you want more flexibility, smaller frameworks like Flask or Pyramid work fine.
If the developer writes code that handles credit card information, absolutely. Most organizations utilize third parties to handle credit card info so they don't have to be PCI compliant. Even then, it helps to know something about PCI because the developer may be storing more information than needed.
In general I think every developer should receive secure coding training. Most developers don't...
Not necessarily. If you do a test with good SQL and a second test with SQL Injection and compare the responses that can show SQL Injection exists without having to change the database. This won't work for all SQL injection tests, but I would rather take this approach first.
Yeah, I would make the SQL injection and command injections test a little less kinetic =). Using a simple SELECT test, like SELECT @@VERSION, would be a little safer... Edit: Forget to say thanks! This is a pretty cool list.
+1 for Python. You're probably aware of a company called Sonatype that does something like this during the dev process. Their business is growing fast. As far as I know nobody is doing this in production. I think you've found a nice niche that has a lot of potential. Good luck.
Oh yeah I know, I think there's value in what you're trying to do. I would pay 9/m if it also covered application dependencies. I was just curious how it works. What's the time between CVE release and getting a notification from your service?
You have to embrace the suck. I felt the same way for a long time, but as long as you are learning on every project you'll get better. I used to be very self-conscious about my code...I guess I still am a little. I stopped trying to do more projects and focused on one or two. Keep doing revisions until it starts to look good and you feel good about it.
A few years out of college, I was working at a startup building UAVs. It was pretty awesome. We had to move for me to take this job and my wife switched schools for the move. After 2 years she wasn't happy and wanted to move back to her original school to finish her degree. In order to make the move happen I had to take a programming job that was horrible. I was doing .NET web sites and babysitting a SharePoint server. Horrible, but I did it for my wife. I thought I would have to explain the blip on the radar in the future. While I was at this job, I met a guy who was a consultant for a silicon valley startup. He talked me into joining their company. That was 7 years ago. By taking the crap job, I found a dream job.
I've worked for a major static analysis product company for 7 years and I can tell you from experience customizing rules is not a popular feature. People like the idea of writing custom rules, but the vast majority don't. You guys may make a market out of this and prove me wrong wrong, I just wanted to provide some feedback based on my experience in this industry.
It depends on what you want. Are you looking for experience? To pick a winning horse? The important part of any job decision is to decide on what you want. This sounds basic, but for every job decision I've ever made I started with a statement of what I want and then did a pro/con list. I assigned a value to each item and derived a score. It's really easy to get caught up in trying to make the "right choice". I don't regret any of my job decisions, so it's worked for me. Might work for you too.