menu

Stepsize

Stepsize is a SaaS solution to measure and manage technical debt. Join our new community and kick off a conversation!

Channels
Team

Stepsize watercooler

September 3, 2019 at 10:38am
Show previous messages

November 28, 2019 at 1:43pm
We might need to do a better job to make that clear, but the main aim of the extension is to draw your attention to functions rated D / E with many issues. A function rated A or B is generally considered good enough, and even if one or two metrics are yellow there are typically more important things to worry about. Is that the impression you have? Or do you feel like it pushes you to make every piece of code green all around?
  • reply
  • like
, thank you for being attentive. I haven't take a look at the metric; I have experience only with the colored values presented to me within my IDE :)
I would definitely take a good look at refactoring blocks rated D and E. My initial impression was that blocks rated B (maybe C, too) are good enough, but the fact that the extension brought it to my attention meant that there was something wrong with my code. I'm sure everyone has different reactions. I'm always looking for different ways to be a better coder which is why I wanted to ask about the comment density.
  • reply
  • like
If I hadn't spoken with you I think it would have bothered me to not have all green code all around.
  • reply
  • like

November 29, 2019 at 7:33pm
thanks again for taking the time to share your thoughts! We've just finished our planning session for next week – based on your feedback and those of others we'll make some tweaks to the comment density metric which should result in it being green for snippets like the one you sent πŸ‘Œ
  • reply
  • like
We don't have immediate plans to tweak the nesting metric or to make the metrics' thresholds configurable, but it's something we're thinking about. The main reason is that we're trying to present an objective view of code quality based on empirical research, and this isn't quite compatible with configurable thresholds. But these are early days, your feedback has been well received and will be considered for anything we do next πŸ™
  • reply
  • like

December 10, 2019 at 7:52pm
Hi! https://www.stepsize.com/ does not unfurl on Slack.
like-fill
1
  • reply
  • like
just wanted to share in case this is not something you are already aware.
  • reply
  • like
just wanted to share in case this is not something you are already aware.
Hi Augusto :) thanks for letting us know! Really kind. Just to confirm, are you referring to the URL preview? If so, when you share other URL’s, I assume they preview normally?
  • reply
  • like
Yep sorry i wasn't clear. See for example how https://terms.stepsize.com/ does have a preview.
  • reply
  • like
Got it! Thanks again. We’ll look into this :)
  • reply
  • like
Let me know if there’s anything else you’d like to point out about the extension. I hope you’re finding it useful !
  • reply
  • like

December 12, 2019 at 11:42am
Hi πŸ‘‹. The issue with the URL preview should be fixed now. Not a game changer, I'm sure, but just letting you know 😊 Thanks again for reporting it.
  • reply
  • like

January 17, 2020 at 9:53pm
Hi, is there a way of logging tech debt (more specifically: design debt) based on TODO comments? So far it is only recognizing function complexity which isn't too helpful to us.
like-fill
1
  • reply
  • like

January 19, 2020 at 6:43pm
Hey πŸ‘‹ thanks for getting in touch, I've replied on our feature request board https://stepsize.canny.io/tech-debt-tracker-feature-requests/p/design-debt
  • reply
  • like

February 3, 2020 at 11:31am
Hello Stepsize !
I was looking for a Debt Tracker Software and i ran into your plugin. I must admit it looks really appealing and i will definitively install it (Big up for the team btw) ! :)
I want to implement this in my team workflow, unfortunately, a part of team is working on IntelliJ IDEA. Do you plan to make the plugin on this IDE too ?
like-fill
1
  • reply
  • like

February 3, 2020 at 6:36pm
Hi, is there a way of logging tech debt (more specifically: design debt) based on TODO comments? So far it is only recognizing function complexity which isn't too helpful to us.
Hey , we're working on an update to empower engineering teams to track & discuss design debt (although it's not based on TODO comments). I'd love to hear your thoughts on it if you have a moment πŸ˜„ Feel free to DM me
  • reply
  • like
Hello Stepsize !
I was looking for a Debt Tracker Software and i ran into your plugin. I must admit it looks really appealing and i will definitively install it (Big up for the team btw) ! :)
I want to implement this in my team workflow, unfortunately, a part of team is working on IntelliJ IDEA. Do you plan to make the plugin on this IDE too ?
Hey , thanks for getting in touch and for the kind words 😊
Edited
  • reply
  • like
We're not currently working on supporting other editors / IDEs, however we are trying to make the tool more useful to teams and help them identify, discuss, and prioritise technical debt in a more powerful way. Would you have a moment to tell me more about your team's needs? It'd be really helpful for me to understand them better, and I can also run our current work in progress by you to refine our direction πŸ˜„ Let me know and feel free to DM me ✌️
  • reply
  • like
Hi would love to see what ideas you came up with.
like-fill
1
  • reply
  • like

February 5, 2020 at 12:56pm
Hello , Thank your reply !
I will check a bit how the plugin is working and will discuss it with my team and i will come back at you to talk about it !
  • reply
  • like
Sounds great , thanks πŸ™Œ
  • reply
  • like

March 25, 2020 at 3:58pm
Hey! I am quite confident with this extension / tool although I'll be waiting for multiple git support
Edited
  • reply
  • like
Hey! I am quite confident with this extension / tool although I'll be waiting for multiple git support
Hey ! Thanks for reaching out πŸ˜„Could you clarify what you mean by multiple git support please? I'm not sure I get it πŸ™
  • reply
  • like