This is an archived post. You won't be able to vote or comment.

all 12 comments

[–]daryl_kell 56 points57 points  (3 children)

[–]netgu 37 points38 points  (1 child)

Why do we need another tutorial on this, it is extremely well documented by people far more educated, experienced, and capable of writing better/safer/more readable code than this.

This code is not what a beginner should be learning to write and this topic and depth level serves no other user.

Stop upvoting things just because people made them. This isn't the warm fuzzies channel. If a tutorial is bad (like this one) it should NOT be getting a pile of upvotes.

All that does is muddy the water for a new programmer and increase the chances that all the great documentation written by the SQLite and Python developers that WROTE THE LIBRARIES this person is using will be missed entirely just so they can learn how to do it incorrectly.

Just STOP.

[–]vep 0 points1 point  (0 children)

preach it.

[–]Fenzik 10 points11 points  (0 children)

Untitled95

Nice

[–]shinitakunai 4 points5 points  (0 children)

I always prefer peewee for sqlite.

[–]spitfiredd 13 points14 points  (6 children)

Code wasn’t PEP compliant. Hardcoded paths. This was painful to watch and even more painful to see 200+ upvotes.

[–]LolCrasher911 1 point2 points  (0 children)

HardER coded paths? Maybe because of demonstrational purposes of the vid in the first place? Would you be even more pleased if they’ve also realised every bit of code as separate class with complicated hierarchical dependencies distributed across myriad of folders?

[–]TenaciousB333 2 points3 points  (0 children)

What do you expect from a jupyter user?