Skip Navigation

User banner
Posts
6
Comments
488
Joined
2 yr. ago

  • C is for Canada.

  • Oh god

    Jump
  • Well.. it's a door. At least my ass will be closed for business after that.

  • Loud, energizing music will calm you by feeding a steady stream of dopamine.

    Sadly this is also why I can fall asleep at a party after a coffee.

  • Trial at Bernies? OK WERE DOING TRIAL AT BERNIES! This is going to be legend-wait for it....

  • The beauty is that you can shove Pi in it of course.

  • Hence the groups having the ticket name related to the task I am working on. When the task closes I delete that group once I've ensured anything important for future context is documented and then I say goodbye with confidence.

    I don't bookmark things for work tasks, I log them in tickets or commit it to readme/code comments/team docs somewhere.

    Edit: I should also note that my workflow uses Simple Tab Groups and not much of this new core feature.

    Simple tab groups hides all other tabs and you switch groups via a dropdown. I usually only have 10-12 tabs open at once.

  • It's Twitter in a trenchcoat saying "whats up fellow fediverse apps".

  • Agile and task reprioritization at work.

    Too many projects to work on at home.

    Games.

  • The way they did it though.. the tab group name cant be collapsed so it takes a lot of room. I find I'm still using task oriented groups from the Simple Tab Groups extension, and then using the new core groups feature as a way to group subtopics for that task.

    And before you say "you must have a million tabs".. I used to have millions of tabs, but now i average less than 100 when I have a lot of tasks I need to balance, and I know what all of them are open for. So when I complete a task I delete the Simple Tab Group and say bye to all those tabs.