furstenheim

15 ms·

121.
by furstenheim 6y ago
This one was super useful for me https://www.amazon.es/PostgreSQL-High-Performance-Gregory-Sm... I think that they have a newer edition for postgres 10
122.
by furstenheim 6y ago
For the later interviews, once you're left with a couple of candidates to decide from, I like product driven interviews. You choose a complex business requirement that is already implemented. You discuss different architecture options,
123.
by furstenheim 6y ago
Of course, I'm not saying the opposite. But you're sacrifying development options in the process
124.
by furstenheim 6y ago
One thing that bothers me about serverless functions is that there is virtually no concurrency. Once you return you have no assurance that your code will keep on working. If you want to perform actions that might be throttled (cloudwatch fo
125.
by furstenheim 6y ago
Alternatively, you could have some ui that allowed writing to the wiki and it converted it to a commit. Basically the same way that editing the readme can be done at GitHub. In any case, as mentioned in a different comment. Most of the wiki
126.
by furstenheim 6y ago
Take a look here https://hnhiring.com/ it might be helpful
127.
by furstenheim 6y ago
How ironic, one of the first things that I missed in Java was that. Nor the compiler error, nor the standard linter (checkstyle) prevents unused variables.
128.
by furstenheim 6y ago
What they said is that if it's gummy, it will induce you to chew during the night. They claimed that the only approved one was hard, but I didn't verify that. I have less pain. But I won't risk sleeping without it
129.
by furstenheim 6y ago
A lot of the results of this analysis are a consequence of actually good UX in dependency management. In NPM publishing a library is really easy. To compare with java, I recently had to follow a [three part medium article]( https:/&#x2
130.
by furstenheim 6y ago
Same here. I have the impression that it has improved by a) having a softer pillow. b) having a hard guard. Before that I had a gummy-like guard. According to the new dentist the was making the bruxism worse.
131.
by furstenheim 6y ago
Very interesting. I'm starting now a project to organise my recipes. With https://github.com/domchristie/turndown it transforms the html from clipboard into markdown, they result is really good and it's gener
132.
by furstenheim 6y ago
I'd rather track it in the repo and let the pipeline deploy it. No need to modify it by hand.
133.
Show HN: Annotation based parser for programming contest inputs in Java(github.com)
1 points by furstenheim 6y ago|0 comments
134.
by furstenheim 6y ago
You can always move it to a variadic function and do await parallel(first, two) If your concern is clunkiness, I'm curious about callbacks, they're definitely more complex to use. I understand your point that not knowing
135.
by furstenheim 6y ago
Parallelizing is plain simple "await Promise.all([first, second])" Problem is doing some serious synchronization like n at a time or similar. Those things are better of with callbacks
136.
by furstenheim 6y ago
Hey, I just saw your comment. For the jsonb `INSERT INTO some_table (a, b) SELECT x.a, x.b FROM json_to_recordset('[{"a":1,"b":"foo"},{"a":"2","b":"bar"}]') AS
137.
by furstenheim 6y ago
Oh please, no auto casting. It's given way more problems that those that have solved (looking at you Excel). If you want to use json, validate, and accept both 10 and "10" you can use json schema and do: ``` { "type&quot
138.
by furstenheim 6y ago
The user does care. At a previous company we started migrating from angular to vue. Vue was so fast that those parts would be completely rendered and the rest would be white. It was also snappy. Of course, one has to be mindful about the tr
139.
by furstenheim 6y ago
There are nicer ways to do batch insert in postgres. With 'jsob_to_recordset' there is only one parameter which is an array and it gets queried as a table. That has the advantage of avoiding different queries for different inputs
140.
by furstenheim 6y ago
- tests in watch mode. Either with --watch if I'm doing js with mocha or inotify if I'm doing another language. Tests or compile should execute on save, which in turn I configure in autosave. - making sure that I can execute every
141.
by furstenheim 6y ago
Writing a service thinking that you'll throw everything away is a waste of time. And so is trying to get everything perfect, because you don't yet understand the business correctly. In my experience you should not treat all parts
142.
by furstenheim 6y ago
I think it's important to find feasible projects. A full stack project will probably be left unfinished. A way to find projects is to do tasks that you'd at work if you didn't have deadlines and were allowed to do more explor
143.
by furstenheim 6y ago
Something that works very nicely. If the branch is always on the shape ticket-description, one can write a git hook so that all commits have the ticket name preppended to the name, like in "[ticket] commit text", very useful for u
144.
Show HN: A Golang encoding for code competitions(github.com)
2 points by furstenheim 7y ago|0 comments
145.
by furstenheim 7y ago
"however, if you want to make sure you have the same experience as your users, I'd recommend to add it to .gitignore." That's just plainly wrong. Lock files are ignored in libraries so that shared common dependencies can
146.
by furstenheim 7y ago
Geoblink | VP of Engineering, Principal Software Engineer | Madrid, Spain | Full-time | Onsite https://geoblink.com Geoblink is a fast-growing startup that has already raised close to $8 million in investment from leading ventur