mxz3000

8 ms·

31.
by mxz3000 5y ago
> Ignoring the fact that relational databases and SQL are permanently entrenched, an alternative database technology cannot succeed unless it also supports a high-level query language. The advantages of such a language are just overwhelm
32.
by mxz3000 5y ago
What do you mean? If you compose functions (and objects) together then you have to mock things out one way or another, inject them in, and assert that your code interacts correctly with its dependencies. This doesn't seem like a go spe
33.
by mxz3000 5y ago
But you can obviously DRY without inheritance? I'm not sure that Go pushes you to duplicate code... Do you mean copy a slightly tweak code for different use cases and types ?
34.
by mxz3000 5y ago
That made me chuckle
35.
by mxz3000 5y ago
100% this. You can fix lots of small issues that would otherwise just be noise on the PR just by reviewing it yourself beforehand, as if it was somebody else's code! When I onboard junior engineers, this is one of the things I tell the
36.
by mxz3000 5y ago
In my experience, most APIs my teamed designed/built were not meant to ever be publicly available. That is, we never considered public availability as a design factor. So I think this rule doesn't actually apply anymore. Then agai
37.
by mxz3000 5y ago
Not all companies/teams have dedicated QA and Ops teams. In the (very large) company I work at, the engineers are responsible for writing the code, testing it, and supporting it once it's live. That includes being Oncall and being
38.
by mxz3000 5y ago
Tbh, That's why for our new projects we've completely ignored relational databases. They're a pain in the ass to manage and scale poorly. DynamoDB, on the other hand, trivially scales to thousands (and more!) of TPS and doesn
39.
by mxz3000 6y ago
The given, when, then breakdown is interesting, though I've never seen language test utilities actually enforce that structure. Maybe an interesting potential experiment (regardless of language) ? I feel like your last point is especia
40.
by mxz3000 6y ago
This. This allows sensitive data to never leave the storage layer.
41.
by mxz3000 6y ago
I'm more than happy to lose the jack to get a bigger battery or thinner/lighter phone. I'm never going back to wired headphones anyways, wireless is the future. Far too used to not having my head tethered to my phone (or lapt
42.
by mxz3000 6y ago
Working with multiple AWS accounts is definitely a pain, but it definitely should get better in the future given that it's a super important use case for internal services. Internally we have best practices that dictate to split servic
43.
by mxz3000 6y ago
Do people actually use UML in industry? I've never actually seen it used (or mentioned for that matter) in the few years I've been a software engineer...
44.
by mxz3000 6y ago
If you're going all in on AWS, I'd recommend trying out CDK!
45.
by mxz3000 6y ago
They definitely didn't replace oracle with dynamo, those are very different beasts and would require complete redesigns of the migrated service. RDS sounds much more appropriate/realistic.
46.
by mxz3000 6y ago
That's where AWS CDK comes in, it's great. Infrastructure as (actual) code.
47.
by mxz3000 6y ago
Typescript is the best supported language.
48.
by mxz3000 6y ago
CDK is amazing, we use it in typescript and it's just great, so much easier than raw cloudformation or SAM. I can't compare to TF as I have no experience with it, but I would assume CDK is better just because you can use a well es
49.
by mxz3000 6y ago
I took this course during my time at Imperial. Tom Clarke is a great lecturer, and is actually passionate about teaching (which cannot be said about other lecturers...)
50.
by mxz3000 6y ago
Totally, cloudformation is terrible and verbose. [Cloud Development Kit]( https://aws.amazon.com/cdk/ ) however, is superb.
51.
by mxz3000 6y ago
That's a pattern I use in a lot of Typescript, it's pretty useful!
52.
by mxz3000 6y ago
This is exactly the sort of problem solved by cdk: https://docs.aws.amazon.com/cdk/latest/guide/home.html with cdk you generally don't have to mess with IAM constructs, and can just use the provided APIs
53.
by mxz3000 6y ago
When you're Oncall you aren't Oncall 24/7 forever. It usually rotates amongst the engineers in the team. I'm on a team with about 10 engineers in it so you're on call about a week every two months. I call that manag
54.
by mxz3000 6y ago
Dynamo is great. All new projects I work on that require a db use it. We're slowly moving away from SQL databases entirely. Far more scalable, no more horrible SQL issues, at the cost of not being as flexible. But that's alright i
55.
by mxz3000 6y ago
I guess the main issue is that languages outside of English generally don't have equivalent words for all of CS terms. I always have trouble explaining what I do (software engineering) in French without resorting to using English words
56.
by mxz3000 6y ago
Cheaper/faster hardware probably
57.
by mxz3000 6y ago
Faster/cheaper hardware probably
58.
by mxz3000 6y ago
Not op, but I have experience with TS and some things are more difficult than they should be. For me the biggest issue is the lack of typesafe deserialisation. This makes it super painful to do IO (of which there's _a lot_ of in the se
59.
by mxz3000 6y ago
+1 for CDK. It's the way forward. CloudFormation sucks.
60.
by mxz3000 6y ago
I routinely go over 10GB of ram with a bunch of chrome tabs, IDE windows, Spotify, chat app, outlook, etc... It's really not hard.

More ›