I strongly disagree. We treat chickens quite poor.
Laying hens for example, we throw most male chicks into a shredder because they can't produce eggs. That's beyond cruel regardless of their mental capacity.
Another example. Chicken debeaking is a practice used to prevent chickens self mutilating or destroying their eggs or each other.
You're quite correct. My team just inherited a large node codebase that had proxy sprinkled everywhere, complete with a custom undocumented dsl written using proxies. It was a nightmare to learn, hard to extend without breaking and resulted in quite a few refactoring sessions.
I think proxies have their place, but most apps don't need them imo
This seems quite odd to me. I work with people remotely and on site, and it's amazing how much better communication is when both parties turn their webcam on. Body language conveys things that tone, and words don't
They are both types of chats. We use a combination of skype for business and zoom (zoom supports external people far better than skype, and actually works better in all regards).
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.
While i'm not 100% remote (i'm part of a small regional office that has a massive head office in another part of the country, but I can work from home). Something i've found incredibly important is jumping on video chat. There's something about seeing someone in a video while you talk to them that reminds you "hey i'm working with other humans, i should respond with a level of empathy i'd expect in return"
My experience so far is, i've made more opportunities for myself going to the bar/pub/coffee shop after a meet up to shoot the shit with my peers than anything i've ever put on my resume.
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
Requiring apple hardware to develop for ios is a pretty big reason to prefer mbp over pixel. Even if you aren't an ios developer, a development shop that does mobile will most likely deploy macs to their developers.
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.
Thanks for the tips, I'm still ramping up on ios development and the apple eco system with a deadline I barely managed. I'll take this into consideration for the next Sprint.