You must log in or register to comment.
The older I get the more impatient I get with stupid tasks that take longer then they should. I simplify my life by focusing on the task ahead of me. Knowing these small tasks compound into the final goal.
So when I am looking through 17 different folders for a file I can’t remember what I saved it as and I’m sorting by date and opening things frantically…
‘it’s been 20 fucking minutes, should I just take the rest of the day to organize my shit? But if I get this fucking thing done I can setup a meeting on this today and fit it in this week before Juan goes on vacation and I have to wait two weeks to place an order that will take 6 months to deliver.’
‘Fuuuuuuuuu where the fuck is this file, I’ll just start from scratch and I’ll be done by 2pm just in time for it to go on the calender so everyone can seee. Or maybe i just look another 15 minutes wheeerreeeee the fuckkkk did I save this?!?!’
'Bullshit bullshit bullshit!"
Google: how to find file.
Google: how to find file just working on.
Google: how to find excel file by date, most recent.
Google: file not in recent, why come?
Google: did I dream a this nightmare wake me, wake me, wake me.’
This literally happened to me yesterday, but with filenames. I was failing to configure a program until an hour later I found out that I mispelled the config file as
colors.iniinstead ofcolor.ini.I like that even here on Lemmy, with inline code format,
colors.iniis not being colored butcolor.iniis. Great symbolism for your issue.
…for people who refuse to use static types.
Static types are great, but not exactly what would have helped here, any decent language or at least a linter should catch the use of a not declared identifier.
def foo(x): return x.whatevrNo linter is going to catch that.
class MyClass: def __init__(self, x: int): self.whatever: int = x def foo(x: MyClass) -> int: return x.whatevrAny decent IDE would give you an error for unresolved attribute. Likewise it would warn you of type error if the type of
x.whateverdidn’t match the return type offoo()Yes because you used static type annotations. This thread was about code that doesn’t use static types (or static type annotations/hints).
Python doesn’t check the types of function headers though. They’re only hints for the programmer.
OP suggested that linters for python won’t catch attribute errors, which they 100% will if you use type hints, as you should.
What happens at runtime is really relevant in this case.
Linters 100% won’t. A static type checker is not a linter.
I don’t want to get into an Internet argument over pedantry. Linter is often used as a catch-all term for static analysis tools.
Wikipedia defines it as
Lint is the computer science term for a static code analysis tool used to flag programming errors, bugs, stylistic errors and suspicious constructs.
Catching type errors and attribute errors would fit under this description, if you use a different, more precise definition at your workplace, cool, then we just have different definitions for it. The point is that your IDE should automatically detect the errors regardless of what you call it.
You’re both right. It’s possible to write code that gets linted well in Python, yes, but you’re often not working with just your code. If a library doesn’t use typing properly, not a lot to be done without a ton more effort.
It’s python, just use type hinting already and your linter will catch that.
Also some winters can look at the use of food and see the type being passed in.
Autocorrect got you pretty bad, there.
I was very confused, why we’re suddenly talking about rationing food during winter. 🙃
Holy crap that’s wild, new phones autocorrect is out to get me
Yes you can use static type hinting and the static type checker (Mypy or Pyright) will catch that. Linters (Pylint) won’t.
Not with an example that simple and poor, no.
If you have done the minimum and at least set a type hint, or if your ide is smart enough to check what calls the function and what it passes, then it’ll be flagged.
Always love seeing the trope:
*writes awful code*
See! This is why this language sucks!
This is literally a getter function. How is a getter awful code? It’s the simplest function there is. The only function simpler than that is returning the input itself.
How does “foo” mean “get”? Half the battle of writing correct code is writing code that’s easy to interpret. Do you always look at the guts of every function you’re about to use?
It’s a one line function in an example. It’s a getter.
How would you make it non-awful, without specifying static types?
I guess, a unit test would catch it, but needing 100% test coverage to catch typos isn’t exactly great…
I use a spell checker in my IDE. It would catch this.
What’s awful about this example? The only thing I do is access an object member. Does your code not do that??
What’s the purpose of foo? Why an ambiguous single character variable? What if the property was there but the value was null? Why not use (assuming JS) optional chaining?
I’d approach it more like this:
function getWhatevrProp(userData) ( const default = { whatevr: "n/a" }; return { ...default, ...userData }.whatevr; }Sorry, read too fast the first time. It’s more likely Python. I also don’t know Python well enough to give recommendations on that.
Lmao, and they say dynamic typing is supposed to speed up the developer.
It’s an example to demonstrate that linters cannot reliably detect variable name typos - you need static types. None of the stuff you mentioned is relevant.
The typo in your example is also undetectable by linters. I think you’re missing the point.
I appreciate the “carrot with a bit out of it” icon.
I’m in this picture, and I don’t like it.
No I’m Spartacus.
I didn’t sign a release!
The problem is the client 🤣
If you remove the 4th panel then this accurately describes call center customer service
I spent like 3 hours yesterday deduplicating two functions that were hundreds of lines long and nearly identical. I should probably learn how to use that git command that can diff two files on disk. Luckily I actually enjoy cleaning up code sometimes.
Dunno what OS’s it supports besides Windows but I use Kdiff for random comparisons regularly, I think it works pretty well untill you get to much larger files (20+ MB slows down a lot). The huge file wasn’t code but needed to check output changes for those curious.
I constantly check git comparison with previous versions to see what changed to break things in a build though. Didn’t know there was a way to diff any files in git,should probably just learn to use that one.
Git uses the
diffbinary under the hood (unless you configure it to use something else).
You can invoke that directly withdiff file_a.txt file_b.txt.
git diff —no-index before.json after.json > showmethegoods.diffYou don’t have to save it to a file but I often do.
If you’re using a decent development system, you’ll have an executable called
diffinstalled already :)That’s what the
difftool is for.If you use VSCode, open both files and then ctrl-shift-P “Compare active file with …”
You’re welcome.
Thank you! I love VS Code
VS Code’s diff tools are killer. Comparison is smarter than most, and you can edit either file as you go.
And if you want to avoid the Microsoft stank, there’s VS Codium that has been de-Microsoft’d, like Chrome vs. Chromium.
You can use a diff app directly such as meld which is free. Highly recommend.
Use spell check in your code editor and never experience this again.
Spellcheck? My editor proposes known words after 3 characters.
Yeah, pretty much
Hey, that’s me! Minus the last panel :)
