devocracy's comments

On: Fortunately, I don't squash my commits

[devocracy]

That's not a squash or not problem, that's a your tickets are too large problem. If you normally end up with 3000 line feature commits, you're trying to do too much with individual feature changes.

[grumple → devocracy]

Are we pretending that we, as devs, have much say in this? If our management says they want a features that’s going to take 3000 lines of code, you don’t have a choice. It’s nice if you’re somewhere where you can roll out feature mvps, but in some environments you don’t get that luxury.

And some features are just monsters, either through the nature of the feature or architectural choices that were made before it was conceived.

[saagarjha → grumple]

Then you split the feature up? It’s generally possible to do this.

[grumple → saagarjha]

I mean, I’m the one arguing for smaller commits, so yes, if you make it 10 commits via 10 prs instead, that’s fine with me. But if all of that has to go out at the same time, that’s not any different than one pr with 10 commits (and probably worse because it’s harder to see all the changes together).

[saagarjha → grumple]

I actually occasionally make those kinds of pull requests and would recommend that over the alternative.

On: Show HN: Tara – A smart and free alternative to Jira

[devocracy]

Make a status for blocked, create a column for that status

[Scarblac → devocracy]

Yes but that needs to be part of a published workflow...

On: Show HN: Tara – A smart and free alternative to Jira

[devocracy]

That was the fogbugz approach, I hated fogbugz as it was too prescriptive

[pookeh → devocracy]

Also pivotal....but pivotal is nice

On: The Siege of Carrie Lam

[devocracy]

It sure would be "unfortunate" if they replaced autocratic rule with a representative democracy.

On: Slack will never replace email

[devocracy]

Is there not value to be gained when someone is struggling to get past a problem? I've seen what happens when people too quickly phone a friend whenever they hit a problem, the end result being they don't round out their knowledge.

[javagram → devocracy]

It depends on the person and the problem I think. I have also seen people sort of struggle and not really make progress and leaving them in their own wouldn’t be a learning experience.

Like how if you throw someone who doesn’t know how to swim in the ocean they might just thrash about until they get tired and drown...

I do always try to work with them to explain the steps I am taking to troubleshoot but it’s definitely a balancing act as you want them to learn not just have it done for them.

On: Google Is Turning Off the Works-with-Nest API

[devocracy]

The Ecobee has been great, simple and just works. I received it for free from some in-home energy program, but I will buy another when I move.

On: Do people become happier after 40?

[devocracy]

Not sure why you're being downvoted, the switch has done wonders for my cardio

On: Lyft Files S-1

[devocracy]

If that were true (I have no info either way), wouldn't that mean most drivers have no clue the true cost of working for Lyft/Uber? All they see if free money, but aren't factoring in repairs.

[buboard → devocracy]

i wonder how long does it take for an uber driver to break even their car

On: Harder programming questions do a worse job of predicting outcomes

[devocracy]

I'm curious to find out what people define as fizzbuzz, do you have a good example of something you've asked in the past?

[toasterlovin → devocracy]

Print numbers from 1 to 100, except print Fizz for numbers evenly divisible by 3, print Buzz for numbers evenly divisible by 5, and print FizzBuzz for numbers divisible by both 3 and 5.

On: GitHub dashboard UI refresh

[devocracy]

That may be true on windows or some flavours of desktop Linux where simple windows management have existed for some time (windows 10 being a real champ of multiple frame management on the same display), but if you're on a Mac you're stuck with a real mess that requires a lot of manual screen size management.