Are they? I don’t see it. They’re more profitable than ever and are still extremely competitive in multiple markets.
The arguments against this have been the same for decades: Apple is overpriced, Apple’s product are inferior to competition, and yet here we are with large chunks of the market share and larger chunks of market gains.
Some products are stupid, but it’s not like Steve hasn’t pushed dead products out before.
Warning is not possible, have you seen the amount of spam the web has?
What’s possible though is a better handling of these scenarios. Don’t lock me out of my entire account, but stop the specific service/action breaking the ToS.
The most interesting part of this tool is that it has enterprise features and it’s still free. I mean why. You’re producing a product to handle large amounts of money and you don’t want a cut?
Sorry but your argument makes no sense. The 10LOC/day guy is not to be singled out from the 1000LOC/day people because 1000 LOC could be just as trivial; 1LOC could have taken hours to discover.
Exactly! I've myself spent days investigating an issue only happening on a specific Android device (but used by an important client) only to find that the solution was something along the lines of using "opacity: 0.1" instead of 0.
That bug was left unfixed for months but now it's solved. Should I have received a talk because of that?
(Of course the commit would have had at least 10 LOC more, explaining the reasons and providing references to future devs/self)
That makes your point clear, but then what you are looking for is not a scalar value (that may be for instance be subject to a proportional judgement) but a fuzzy threshold.
This is exactly why KLoC is not a good measurement. If you know about this, you will make sure you match everyone else by embellishing your line count with comments, copy and rename functions or extra deep nesting. The manager will still not know anything without looking at everyones code.
A good manager should recognize that if a developer does nothing but annotate code with comments, and that's not what they're expected to be doing, there's a problem.
So if you managed a team, and when you look at commit histories you notice that one person has <1 commit a month and you look at the commits and they're trivial... you would disregard any concerns?
The answer is still "it depends", I would imagine that issues would arise well before you had to look at their commit history.
I believe that if you are a good manager, you would just need to look at what tickets get done during the sprint and that's it. If you complete your tickets and pass QA/UAT in 10 LOC, so be it. There is no need to micromanage.
I would wonder how it got to the second month, certainly - getting to the point where this kind of post-hoc analysis can actually be done is a serious failing of management.
I mean, seems highly role-dependent. If, in practice, your role is to investigate and fix very difficult problems, that’s precisely the sort of commit history one might expect.
I wonder what the grandparent would think about a few LOC/month, there were a few rather gnarly performance issues in the codebase at my work for which the fix was usually a one or two liner, but that took an inordinate amount of research to even know where to start looking.
I guess I should be grateful for having a workplace that has sufficient understanding for the effort it takes to debug such issues.
Right. One data point among many. And managers should be looking at everyone’s code, not just the low LOC ones.
But there are people (I’ve seen this frequently) who constantly represent their work as having been “much more difficult than expected” but then you discover that they actually are struggling with what should be easy tasks, and looking at code (complexity and volume) is a data point. For me, more often than not, it serves as a confirmation of a problem I’ve started to suspect.
I'm confused which part of this is so off-putting.
Joe is always the one in every standup saying the thing he's working isn't done yet because he's wrestling "one last tough bug." As a manager, you wonder if the technical problems are really that tough or if Joe is just struggling. Let's look at the commit history... yeah, something is off here, Joe has 1/10th the commits of his peers and they really don't seem more complex in any way, but look rather trivial. Time to talk to Joe and look at these commits together and see what's going on.
So troubling that you can't propose it cleanly: if you've already defined that "they really don't seem more complex in any way, but look rather trivial", why would you need to count? (another troubling sign is going for the order of magnitude assessments, and another minor point: you've mistakenly replaced volume of code with # of commits)
At this point I have PyCharm as my IDE, Obsidian as my official "Notes" with a capital N, and about 40 open unsaved text documents in Sublime Text that i just use as scratchpads. Writing down things, acting as a poor man's extended clipboard, etc.
I absolutely love this flow and it works so well for me now.
I recommend you check out “Scratches” in PyCharm (or any IntelliJ IDE). Cmd+Shift+N I think? I type it reflexively, it lets you create a scratch pad of any “type” (Python, PHP, plain text, shell, everything IntelliJ supports) and write code with syntax highlighting and all the bells and whistles you are used to.
They are all saved in a folder on your computer and easily accessible from the “Scratches” section at the bottom of the file explorer.
It’s my go-to for any text manipulation and I think you can even configure it up to run your snippets of code if you want (I’m stuck using CodeRunner cause I’m too lazy to look more into “running” Scratches).
I also use it to paste in information as I’m debugging a problem. Then I can use multiple cursors or regex find/replace to take information and turn it into commands to run. Yes, I know about CLI tools built in to most systems and I use them to create one-liners but sometimes I want a little more direct control and/or I want to build a script from the commands.
Mostly curious, why do you care about the readability of the generated JS? Surely if you need to debug something for a production bundle you can use source maps.
Are they? I don’t see it. They’re more profitable than ever and are still extremely competitive in multiple markets.
The arguments against this have been the same for decades: Apple is overpriced, Apple’s product are inferior to competition, and yet here we are with large chunks of the market share and larger chunks of market gains.
Some products are stupid, but it’s not like Steve hasn’t pushed dead products out before.