michalc

16 ms·

151.
by michalc 7y ago
Hi, author here. I believe the inputs are already appropriately escaped by passing them through `sql.Identifier`. I have added a comment in the gist about this as well.
152.
Show HN: Django/gevent view to download PostgreSQL table as CSV in single query(gist.github.com)
2 points by michalc 7y ago|3 comments
153.
You might not need a class(charemza.name)
1 points by michalc 7y ago|0 comments
154.
Make skype compatible with iOS 9(skype.uservoice.com)
1 points by michalc 7y ago|0 comments
155.
Show HN: Pure asyncio Python DNS resolver, with no threads and no dependencies(github.com)
3 points by michalc 8y ago|0 comments
156.
Show HN: Throttler for Asyncio Python(github.com)
3 points by michalc 8y ago|0 comments
157.
The Show Trial of the Gang of Four for Crimes Against Computer Science (1999)(laputan.org)
3 points by michalc 8y ago|0 comments
158.
by michalc 8y ago
I like the analogy, but it slightly suggests that you're always powerless along the way and that the debt is inevitable. I think there _is_ a technique that is possible in a lot of situations: not putting in abstractions/complexit
159.
I admit it: I like Python’s ternary operator(charemza.name)
34 points by michalc 8y ago|19 comments
160.
Reducing risk of release day: Large changes do not have to fill you with fear(charemza.name)
2 points by michalc 8y ago|0 comments
161.
by michalc 8y ago
There could be something else at play in the call... they could have been scared that if a representative of Lexus admitted there was a problem with the design, they would be admitting liability.
162.
Aiofastforward: Fast-forward time in tests of asyncio Python code(github.com)
2 points by michalc 8y ago|0 comments
163.
by michalc 8y ago
Hello, author here. Agreed that similar behaviour to the examples can be achieved in different ways. The main aim of FifoLock is to provide a (mini) framework for writing more complex locks. The examples are deliberate in that they show how
164.
TreeLock: Constant-time read/write tree locking for asyncio Python(github.com)
2 points by michalc 8y ago|0 comments
165.
Fifolock: Synchronisation primitives for asyncio Python(github.com)
32 points by michalc 8y ago|6 comments
166.
Python asyncio read/write lock(charemza.name)
2 points by michalc 8y ago|0 comments
167.
You might not need Boto 3(charemza.name)
1 points by michalc 8y ago|0 comments
168.
Questions to ask yourself when handling exceptions(charemza.name)
3 points by michalc 8y ago|0 comments
169.
Arbitrary Mercator Projections(projections.charemza.name)
1 points by michalc 8y ago|0 comments
170.
Structured data in environment variables(charemza.name)
1 points by michalc 8y ago|0 comments
171.
Is the GDPR applicable to data stored in human memory?(law.stackexchange.com)
2 points by michalc 8y ago|0 comments
172.
Programming design choices in the face of changing requirements(charemza.name)
1 points by michalc 9y ago|0 comments
173.
by michalc 9y ago
Good post: although maybe missing a bit on testing? If the manufacturers got a just few people to try to heat up some bolognese, they would probably soon have discovered their UI needs a of tweaking.
174.
by michalc 9y ago
Thinking about this, at the moment, I don't think static typing is a replacement for testing (or vice versa!). Although, apparently, with something like LiquidHaskell, you can get more logic "into" the types and checked by th
175.
Type-simplicity: If you can't have type-safety, have the next best thing(charemza.name)
2 points by michalc 9y ago|0 comments
176.
by michalc 9y ago
I would be interested in reading it... if / when, if you can send me a link, that would be great!
177.
by michalc 9y ago
Perhaps this part is not clear / well defined, but roughly, I meant that code coverage is (about) 100% for the lines added/changed, and some "reasonable" subset of possible breaking changes would be picked up by failing
178.
Questions to ask yourself when writing tests(charemza.name)
203 points by michalc 9y ago|97 comments
179.
Long files are not the enemy(charemza.name)
2 points by michalc 10y ago|0 comments
180.
Non atomic deployments(charemza.name)
2 points by michalc 10y ago|0 comments

More ›