152 karma · joined June 14, 2015
I do agree with the rest of your statements though. Beef farming is far kinder then any poultry farming
I think proxies have their place, but most apps don't need them imo
Our time zone difference isn't as extreme as a 10 hour difference. We have offices -1 and +1 from our current time zone so it makes it easier.
A talk I attended earlier this year had a similar setup to yours and what they did was record all meetings and had a culture of always doing the meeting regardless of wether people could join. Then if you missed the time you chimed in later after you watched the video. Decisions were handled in a similar async fashion.
Your degree is largely just a way to break the ice with some companies, hiring manager x went to school y so he knows that you must be as good as him. Simplified greatly obviously (you still have to know your stuff), but networking is hugely important
I've seen the extremes of 100% tdd and 0 tests, and the most efficient projects/applications are the ones that are somewhere in the middle, you don't need tests for every single thing in your application and it becomes harmful to include them at a certain point.
My Personal preference is to focus on testing "critical" things like business logic, utilities,etc. Then have just a few end to end tests that skate the most important flows. In the end you have fairly tested application and you haven't wasted time asserting trivial pieces.
Since this has linux support i wonder if xcode or something similar will be ported to linux.
My experience so far is that the list of incompatibilities (http://www.oracle.com/technetwork/java/javase/compatibility-...) between versions makes it nearly impossible to just drop code between versions. It will run, but often implementation details have changed causing significant bugs. Your mileage may vary
for example your go problem can be solved using goimports http://godoc.org/golang.org/x/tools/cmd/goimports Using this tool you don't have to worry about those imports and it can be configured to automatically run on save in most editors.
If I have visited your website from a browser there's a good chance that's how i want to interact with you.
I agree that UI is super important, but personally if i find an app is chewing up my battery it's getting removed regardless of its utility. I've also helped a handful of ordinary users diagnose why their battery life is poor. The result is commonly a poorly optimized/buggy app which they uninstall. A dead phone is a useless phone. My experience is primarily android so your mileage may vary on other platforms.
That being said, i think the nature of go routines and how go handles threading could be very important for mobile. We are all walking around with handsets that have multiple weak cores. If we can spread the general work over those cores our handset could possibly get back to a lower power mode faster.
That's my take on it anyways
I liked locust because it was easy to start using, but you write a decent amount of code if you have a complex application. I suggest using pyquery (https://pypi.python.org/pypi/pyquery) with it if you need to inspect any html, it was quite useful
https://github.com/derekparker/delve delve as mentioned other places is more of a true go debugger