You're getting heavily downvoted and I'd love to know why. I've seen similar attitudes toward testing among the groups I've worked with, nobody really wants to do it.
Are folks downvoting this because they don't like testing? Is this idea that prevalent?
> The philosophy of python is there should be only one pythonic way of doing things.
Thiiis really hasn't been my experience with the Python community. Every place I've worked on a Python codebase has done it a different way, and none of them have agreed on what is "pythonic".
Each team has claimed that _their_ approach is the most python-y way to do it, but they've all celebrated Python as not being "restrictive" like "other" languages. It's really weird.
This is a wildly uninformed opinion. People have always written to social norms, and this person is unwilling to acknowledge changing attitudes towards types of writing. I would love a concrete example of the kinds of things this guy thinks are being 'self-censored'.
There are other manufacturers that are building ARM servers these days. AWS even went so far as too build their own chip: https://aws.amazon.com/ec2/graviton/
Morning! I'm a long-time startup developer who's spent the last few years working with small companies helping them get their products launched.
I do everything from strategy to backend development to mobile apps. Most recently I helped a launch a React Native mobile app in the App Store and trained two of their developers on best practices.
I've done Rails, Node, React, React Native, and Ethereum work. Let's work together!
It's a great process for reigning in "great" engineers that produce a ton of technical debt. It's a fantastic approach for making your engineering team more stable and product delivery more predictable.
It's not Scrum. It's Extreme Programming. It works fantastically well, even when you're __fixing bugs__. The whole idea is that you need to be paired so that two people can understand and problem solve around the bug. You end up with twice the understanding that you had before. It's worth it.
Working with other developers, in person. I worked remotely for years. I moved to a new city and I learned so much when I started working on a team, in person, and with other people.
What are good questions to ask during an interview to avoid situations like these? How are other people weeding out employers like this one? This sounds like a bad situation that I'm sure we'd all like to avoid.
I've been in a similar situation, and I think it's about risk. It's relatively easy to decline a job, you're not going to jail for turning down a gig. Not paying taxes will get you some serious jail time though. So morally, yeah, both actions are enabling the same results, but one is easier to commit to.
Are folks downvoting this because they don't like testing? Is this idea that prevalent?