664 karma · joined January 11, 2017
That's similar to coming up with all the code in your head and passing the compiler and tests on the first try without any errors.
Crazy.
The other tag line with breaking a sweat would be much better.
Maybe you should think about it from the listener's POV? For me a podcast has to be interesting or useful. If a title can meet that I will click.
The writing needs work. There is too much. You need to cut down and try to distill the good stuff essence for each episode to make users want to click.
For example,
"QAWolf Helps You Create Automated Browser Tests as You Use Your Site"
-> Automated Testing for your website
The verbiage adds up.
Please do better Google.
Which is insane in retrospect.
Just work hard in school to get out is actually pretty hard. Learning is like swimming through molasses because of the constant stress. It gives you a lifetime of trauma and damage.
I'd also expect their pricing to go down given economies of scale.
I lowkey wanted them to be super ambitious and one day roll out their own chips and become a full stack computer company.
Now after those I lay down and I can't get up for a couple hours with all this aching in my limbs lol.
"How can I sell my software?"
Vs.
"How can I help these folks out?"
What are some things someone like me, an engineer, can do to encourage the government to change the immigration process?
Aristotle influenced the computer is like saying there is oxygen in the air.
I believe it as that's how most of my friends met their partners.
Now everyone and their mom, as well as bots and marketers,can spam right on over.
We either need a search portal with aligned incentives, or perhaps a new internet with none of this crap.
Someone once wrote this. If someone gives you Excalibur, you don't fucking ask where it came from, who made it, etc. Just go use it and have fun.
It's a mix of search space reduction + heuristics. You start looking for most probable areas of fault. This includes new commits. Then you try to partition the places where the bug could be by probablistic reasoning, logging as you go.
If these approaches don't work then you start questioning your assumptions. For example, if there is eatApple() method, what did you assume about this method?
Did you assume all apples are rex, or is the functionality actually eatFruit()?