undefined | Better HN

story

0 pointsuptownfunk3y ago0 comments

I guess I meant what do you do to prevent that from happening.

0 comments

That is my point. I don't have any tools to prevent it from happening. I just don't do it when I write the code. If I have and my code is tested it comes up very quickly.

Us older people tend to keep the whole workflow as simple as possible. That is why I love python. There is very little overhead to just using it.

If you tend to make this mistake a lot it might make sense to add some tooling. I don't need it. If I wanted strict typing I would probably just use C++.

BoorishBears3y ago

I think you're either misrepresenting reality or stretching the truth.

For example, if you're redefining bug as "bug that made it past testing" that's one thing.

But I don't buy anyone writing Python daily for 15 years hasn't seen the term "TypeError" which is what your previous two comments were implying.

mianos3y ago

OK, it's 100% likely I saw it, just so rarely I can't remember.

Testing. Over that long time I have used many test frameworks. My normal workflow is to try and exercise all the code I write as I go.

On the other hand I am 100% pedantic about using 'schema' (https://pypi.org/project/schema/) to validate all the types, structure and domains when I read json.

mharig3y ago

Nearly the same here. The only type error I make a little bit more than I would like, is expecting an iterable and passing a string instead, because I forgot parentheses around arguments.

But I made way more type errors when programming in C/++.

Why do you prefer schema to (fast)jsonschema?

1 more reply

your_neighbor3y ago

You do get type errors, but you catch them with tests? Type hinting catches them without having to write tests.

uptownfunkOP3y ago

So you use some type of testing methodology for your code?

j / k navigate · click thread line to collapse

0 comments

mianos3y ago

That is my point. I don't have any tools to prevent it from happening. I just don't do it when I write the code. If I have and my code is tested it comes up very quickly.

Us older people tend to keep the whole workflow as simple as possible. That is why I love python. There is very little overhead to just using it.

If you tend to make this mistake a lot it might make sense to add some tooling. I don't need it. If I wanted strict typing I would probably just use C++.

BoorishBears3y ago

I think you're either misrepresenting reality or stretching the truth.

For example, if you're redefining bug as "bug that made it past testing" that's one thing.

But I don't buy anyone writing Python daily for 15 years hasn't seen the term "TypeError" which is what your previous two comments were implying.

mianos3y ago

OK, it's 100% likely I saw it, just so rarely I can't remember.

Testing. Over that long time I have used many test frameworks. My normal workflow is to try and exercise all the code I write as I go.

On the other hand I am 100% pedantic about using 'schema' (https://pypi.org/project/schema/) to validate all the types, structure and domains when I read json.

mharig3y ago

Nearly the same here. The only type error I make a little bit more than I would like, is expecting an iterable and passing a string instead, because I forgot parentheses around arguments.

But I made way more type errors when programming in C/++.

Why do you prefer schema to (fast)jsonschema?

1 more reply

your_neighbor3y ago

You do get type errors, but you catch them with tests? Type hinting catches them without having to write tests.

uptownfunkOP3y ago

So you use some type of testing methodology for your code?

j / k navigate · click thread line to collapse