548 karma · joined June 28, 2019
That's very different than popping an artifactory server with a 0day.
I don't care how energy efficient it is. It's dystopian and depressing.
The majority of office jobs are comprised of many simple tasks that current and, to an even greater extent, future, models can handle with ease.
Not all companies are looking for 10x productivity gains. I assume most of them probably just want to do exactly what they are doing now but with lower costs.
2. Leveraging their private APIs will get you banned even quicker than OPs method.
You're going to have a problem getting carriers to sign up because they are assuming all of the risk. Unfortunately, "oh you don't understand - I got paid $27 by CarrierPigeon™ to bring this unmarked, brick shaped package into the country" just isn't going to fly with customs/feds.
There's nothing inherently evil about a knife. Standing outside of a high school and handing a knife to every kid walking in is pretty evil though.
Sounds more like a knock on the person making the comment than it is on me.
That way, I don't care if your branch contains 100 commits or 1 commit. I don't need to worry about commit messages like:
- fix 1
- fix 2
- dfljfdlkfdj
- does it work now?
Do whatever you want with your commits on your feature branch. Just make sure the title of your PR is clean and follows our formatting. Git history is always well formatted and linear.
It's the ideal solution.