kpmah

8 ms·

31.
by kpmah 6y ago
I've had some problems understanding the Laplace transform. Maybe somebody here can point me towards some material. I have an interest understanding how IIR filters are designed, and I always get stuck at this part in DSP books. The La
32.
by kpmah 6y ago
I had a go at writing a type-inferred composable language for database queries a few months ago: https://github.com/KMahoney/squee
33.
by kpmah 6y ago
Very nice! I've recently tried covering some similar ground for a side project ( https://forkjam.com/new ) so I have an idea of how much work this is. I take it you took the approach of using WASM for audio decoders?
34.
by kpmah 6y ago
Except now we have a scientific consensus that the Earth's carrying capacity will decrease. I don't think that's been true before. Expecting technological advancement to bail us out every time is wishful thinking.
35.
by kpmah 7y ago
> Normalization was built for a world with very different assumptions. In the data centers of the 1980s, storage was at a premium and compute was relatively cheap. But the times have changed. Storage is cheap as can be, while compute is
36.
by kpmah 7y ago
I don't believe for a second that your question is 'honest', because I think you're smart enough to be able to type it in to Google and find the answer if you were actually interested in it. Read the IPCC report if you a
37.
by kpmah 8y ago
Yeah, I think I'm confusing storing things as UTC with storing things as UTC+0 - I forgot it stores the offset.
38.
by kpmah 8y ago
Am I right in thinking that if you always store in UTC, when the clocks go back you will get overlapping data? e.g. if you store your logs with a UTC date you'll see interleaving logs for the extra hour, or if you read sensor data or s
39.
by kpmah 8y ago
The difference is interpreted vs compiled, not dynamic vs typed. You can use a C interpreter to instantly run C code without compilation.
40.
by kpmah 8y ago
Looks correct to me. What issue do you have with it? They're saying injection attacks come from dynamically building strings, so if you prevent that you stop the vulnerabilities.
41.
by kpmah 9y ago
This is a really good way of explaining monads. Generally, when people ask about monads, they're not really asking 'what' monads are - they're asking 'why' and 'how' you use them. The advantage shown
42.
Explain Why(kevinmahoney.co.uk)
1 points by kpmah 9y ago|0 comments
43.
by kpmah 9y ago
Types can turn all runtime exceptions in to compile time errors. See: https://www.infoq.com/news/2017/05/elm-zero-runtime-exceptio... I assume you're not claiming that experienced developers never have r
44.
by kpmah 9y ago
I'm learning dutch, and this was a fun way to learn some words!
45.
by kpmah 9y ago
It always bothers me that developers who are working with a team they can't trust to build a disciplined, modular application advocate moving to a more technically challenging architecture as a solution.
46.
by kpmah 9y ago
Forgive me for getting political, but I think Trump was a good non-tech example of 'good because it's new'. Without a voting record and few concrete policies people were free to project their hopes on to him. I have also noti
47.
by kpmah 9y ago
I'm not arguing against using your gut feeling, it is more that if those coders examined why they do things they way they do they could probably come up with some good reasons. And then if you want to convince other people to do it you
48.
Gut Driven Development(kevinmahoney.co.uk)
1 points by kpmah 10y ago|0 comments
49.
by kpmah 10y ago
Not sure how much this will help, but a couple of years ago I wrote about using event sourcing for a simple blog application in PostgreSQL: http://kevinmahoney.co.uk/articles/immutable-data/ I wasn't aware of
50.
A Few Django ORM Mistakes(kevinmahoney.co.uk)
1 points by kpmah 10y ago|0 comments
51.
by kpmah 10y ago
Haskellers tend to be fond of their type system.
52.
by kpmah 10y ago
I think most are pragmatic and admit you may have to do denormalise for performance (e.g. I've read this in C.J. Date's books). I interpret their point as the need for denormalisation is not a flaw with the relational model, but a
53.
by kpmah 10y ago
It depends on the use case you want it for. Unless you're at massive scale, I don't think non-ACID databases are ever really appropriate as a general purpose store. There are niches though. Graph databases, search indexes, databas
54.
by kpmah 10y ago
I would say code for the scale you'll have in the near future, not for the scale you want to have in 5 years. Transitioning database is painful, but dealing with the extra complexity of non-ACID stores can inhibit your growth. If you r
55.
by kpmah 10y ago
In my opinion, the major reason to leave behind ACID databases is if you have reached the point where they can't scale up any more. If you have reached this point, you're probably a company with 20+ developers. There might also be
56.
by kpmah 10y ago
Well, we're playing make believe with the requirements. In fairyland the user and the profile need to exist together. Only the fairies know why! If you can relax the requirements, you can relax the constraints.
57.
by kpmah 10y ago
Do you (or anyone) know of a better example than the bank account? I wouldn't be against changing it. I wanted to communicate through a fairly succinct and understandable example that there are potentially high stakes, and I wanted to
58.
by kpmah 10y ago
Banks are forced to be eventually consistent because of their distributed nature. If it was practical to have a big central ACID database I'm sure that's what they'd use. There is an extra layer of complexity with distributed
59.
by kpmah 10y ago
Yes, be aware of the transactional capabilities of your database. Some ACID databases in their default configuration don't provide all transactional guarantees!
60.
by kpmah 10y ago
I'm not actually that familiar with event sourcing. I'd be interested in reading more if you have a pointer to some resources! Edit: I wasn't familiar with the terminology, but it sounds like what I have written about here:

More ›