stevebot

True, that is one way to look at it, but another is that they are a family providing for each other. It really depends on the agency. As with all things in life, there are good and bad examples. Again, I have had one set of experiences and you another.

I disagree. Apparently, you have had one set of bad experiences with an Agency. I have had a rather good experience.

At an Agency, I am usually brought in for green field projects that larger companies don't feel their team either has the time of expertise for. This is awesome.

Also, at an Agency, I get paid for every hour I work. This is not usually the case in Product Development, where salaries are more common. The caveat, would be if you have equity. Equity can beat being paid for every hour you work, but obviously this is not always the case.

Freelancing also means you usually get paid for every hour you work. However, you also have to spend mad time marketing and looking for clients, as well as managing taxes, heath care and other housekeeping items. I dislike this, and would rather have someone else do it for me.

OP here, I learned a lot from asking this question. Specifically that the Deadlines I have seen fail, were not due to Agile, but failure to implement Agile. Agile takes buy in both from the Customer, managers and dev team. This also takes education on roles and expectations. Without buy-in, you lose the check's and balances and end up with dev teams on a death march, or product deliveries not providing value for the Customer.

Ron Jeffries has a great post on this topic that I highly recommend http://xprogramming.com/articles/jatmakingthedate/

In Seattle, taking a 45 minute train ride can be the difference in 300K or more for buying a house. I wonder if other cities are similar?

agreed, it looks like there is this open ticket:

https://github.com/facebook/stetho/issues/14

Would be really dope if they got that integrated into the elements tab.

How is that really a proxy if it gets compiled into your application? From what others have said it sounds like the real mechanism is over adb.

In my experience, leaving that 70% to Project Manager's usually means giving it up to someone who doesn't understand software. Sure, they might have a business school understanding of what software is, but it's not the same as someone who has been in the trenches and understands software smells.

Ah and I had just finally coughed up 50 dollars for my Charles license. Charles is a nice tool, but this seems so much nicer as I don't see anywhere that the user is required to setup a proxy manually on the phone.

This does make me wonder how their HTTP debugging works? I am assuming that data is passed over USB. Are they using ADB underneath this all?

weird to think about, but what if the scenario had been different and her account was hacked? How would it have gone, would there have been any vindication or recovery or would she have ended up in the same boat?

What is this? I read the first few paragraphs and couldn't keep track of where it was going and lost interest. Can someone explain to me why this is at the top of HN and why I should read it?

god damn, and posting the images to twitter.

You need a new job (as do I probably). There are companies that are not like this, and clients that value developers with exactly these skill sets.

I was lucky enough to start my career at a place which appreciated stable working software and the principle of slowing the fuck down. Then I had the unfortunate experience of changing jobs and ending up at a place where speed was king. Developers were worshiped by their ability to blast through projects. I would call this the "Get Shit Done" principle.

What I have found is that you need a balance. "Slow the Fuck Down" gets you working software, but if that takes you twelve months to a year, you lose the sense of progress and accomplishment that having a live product gives you. There has to be a healthy balance between "Slow the Fuck Down" and "Get Shit Done" which usually involves cutting features, prioritizing and temporary fixes. Most projects using MOSCOW is a good place to start with this.

Applying the God principle to this, there should never be merge conflicts. I should get notified that the file has changed before I even change it. That is how I imagine it would be if a God made it.

I use every bit of StackExchange and have for a few years....except for meta

I use multiple stack exchange sites and even chat and have found it all useful...except for meta

In the few times I have posted to meta, I get downvoted into oblivion. So far, the vibe I get from meta, is that there is an in-crowd with a certain philosophy and if it isn't yours get the fuck out or we will downvote you and pick apart your every word.

It makes me wonder...as a help forum what the hell is meta really for?

Also congrats to SE, glad to see them get this funding...but please wtf is meta?

I feel the same way, but whenever I vocalize this viewpoint on meta I get downvoted into oblivion and wind up deleting my post.

I remember when it first came out and developers in my area would kind of gloat over it and being one of the chosen "glass explorers". they would wear it to meetups and brag about the apps they were developing for it.

I'm kind of glad that it flopped in its current form and that those days are over.

and their API too! https://developer.forecast.io/

heh I love their openness and I also love their app and API. From a consumer perspective, I'm happy for them and hope they don't go away anytime soon.

And in case you're not aware their hourly feed has kick ass data that is amazingly accurate.

There is that fear that you are always replaceable and your job will be outsourced. Because of that there is constant belittling and critique.

It all comes down to insecurity.

It strikes me that most of these points can be automated (well depending on the language perhaps). I prefer automating and blocking checkin's based on criteria like these. Leave code reviews for design discussion.

The problem I have found is not early optimization, but knowing what to optimize early and what can wait. Everything in a system can be optimized, but there obviously isn't the time to do this.

I work in Android, so optimizing I look at first is bitmap loading, backgrounding tasks, and sqlite queries. Usually, this is where 90% of the performance benefit comes from.

heh not sure if this is true, or just some self promotion maybe?

You missed my point. People are prepared to talk about their resume, but when you dig in to their past experience and specifics that is where you get to the interesting discussions.

Case and point:

Tell me about a design pattern you used on X project?

A singleton? Ok, why did you use that?

and a long discussion about testability and architecture ensues with questions from both sides. That is WAY more like the communication that happens on the job than a contrived problem which in many cases is disconnected from real life constraints.

I would much rather hear about their past projects and have them clearly convey design decisions that they made before then have them work on a "on the fly" question. Everybody has off days, not many people have whole off years or careers. Just because I can't design Monopoly in one hour on a certain given day doesn't mean I do not have the relevant experience in my past, whether it be professional or as an undergrad.

percent of acquisition emails that I click through: zero

They recently created uniforms for the Seattle Police department here. Its nebulous what they hope to accomplish with the added surveillance and personally it freaks me out.

I'm not saying were an Orwellian police state but at least we are headed that way.

Just curious though for these specific examples as it says "if you read the source", could these intent's change in future releases, or is it documented outside of the source and accepted that using these intents is not relying on Android internals that could change?

Yes, lack of auto-build, plus no problems view!

However, i've found that i do not notice that so much and get much more benefit from gradle then ant. Also, the project structure has ended up being alot cleaner and easier to navigate for me. Plus, I like all the slick IntelliJ style features.

As for the giant effort to switch? I'd say gradle is a big one.

From someone who uses both daily, this is far from the truth, and I can only conclude that you have not used Android Studio in your day job.