Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
wsy
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
20 ms
·
181.
▲
by
wsy
8y ago
In my experience, you can't learn that skill by watching others. It is a practice, like playing chess, or writing Math proofs. So IMHO the only way is to train. Start with simple problems, and continue from there. Bang your head agains
182.
▲
by
wsy
8y ago
After having read a bit, I'm a bit disappointed. While the intent goes in the direction I would like to see, the actual execution does not follow scientific principles. "Consultant collects some data, derives conclusions, and writ
183.
▲
by
wsy
8y ago
Taking the following steps should help: 1. If you imagine the knowledge in your field as mountains (like the Rocky Mountains, or the Alps), then you need to describe very clearly where exactly your contribution is located. Which summit do y
184.
▲
by
wsy
8y ago
Thanks a lot!
185.
▲
by
wsy
8y ago
Do you have some pointers to important papers of this field of study?
186.
▲
by
wsy
8y ago
YAGNI is a sad example of the state of software engineering: our field follows rules of thumb, based on anecdotes as evidence. When will experimental validation become best practice, like in the other engineering disciplines?
187.
▲
by
wsy
8y ago
Think of your PhD not as as finding solutions for a specific problem you have in mind, think of it as working in a specific area of research. Like with a startup, you usually have to pivot your research because things don't work out as
188.
▲
by
wsy
8y ago
This article has some true observations, but the conclusions seem to go in a totally wrong direction. Writing a PhD is a very ambitious endeavor. You will inevitably have your downs and crises, because research is hard. This is independent
189.
▲
by
wsy
8y ago
In addition to all the good advice already given: this question has (at least) three different dimensions: - what would be best for your company? - what would be best for your team? - what would be best for you? Try to come up with answers
190.
▲
by
wsy
8y ago
Ah, here I disagree. Architecture is usually influenced not only by the software requirements, but also by many non-technical constraints (how is your development organization structured, how skilled are the devs, how sure are you that requ
191.
▲
by
wsy
8y ago
Thanks for the info, looking forward to your new project!
192.
▲
by
wsy
8y ago
I agree that we need more empirical investigations of software 'diseases' and 'cures'. That being said, practical medicine is much less scientific than many think. There is a lot of master/apprentice learning going
193.
▲
by
wsy
8y ago
I don't think so. For example, the Linux kernel is old, but still quite well maintainable. So I would say: it applies to systems where proper modularization was neglected. In the anecdotical cases I referred to, one major element of t
194.
▲
by
wsy
8y ago
Could you elaborate a bit more? If your database is a cluster, then it is still conceptually one database with one schema. You can't migrate one node of your cluster to a new schema version and then move your traffic to it. If you have
195.
▲
by
wsy
8y ago
I really like this suite of projects, it splits the problem nicely into flexible building blocks. How do you envision integration of existing external OAuth2 or OpenID Connect servers, such as Google, GitHub, etc., or an OAuth2-compliant di
196.
▲
by
wsy
8y ago
> It’s easier to just press a button and have your application go to all of your servers based on a deployment group. It's not so much about the deployment process itself (I agree with you that this can be easily automated), but rat
197.
▲
by
wsy
8y ago
Yes, they do fine as examples. I have worked both on decades old booking systems and banking software. Both were dependency hells. Refactoring was impossible. Everybody was super-careful even with tiny changes because the risk to break some
198.
▲
by
wsy
8y ago
You will end up with something like OSGi. That can be the right choice, but is also a quite 'heavyweight' architecture. For a certain class of applications and organizational constraints, I also would prefer it. But it requires a
199.
▲
by
wsy
8y ago
It's exactly the other way around: If you can afford all your components sharing the same database without creating a big dependency hell, then your problem is _too small_ for microservices. If your problem is so large that you have to
200.
▲
by
wsy
8y ago
And still nobody would argue to pack everything together into one executable because of these issues. As everything in software engineering, it is about finding the right trade-off.
201.
▲
by
wsy
8y ago
It's a bit like asking to replace medical doctors with science and theory. We need science and theory, and skilled architects who can apply it to the problem at hand.
202.
▲
by
wsy
8y ago
Nobody fines ICANN. A German registrar doesn't fulfill its contract with ICANN anymore. ICANN sues them at a German court to fulfill it. The court rules that the contract clause is illegal according to German law, so the registrar is n
203.
▲
by
wsy
8y ago
Is the balance of your bank account recorded publicly? So it seem there is no need for a public record. And GDPR does not prohibit voluntary owner entries into a central whois directory, it just prohibits transferring personal data without
204.
▲
by
wsy
8y ago
It's acting in their peoples's best interest. Why should EU be nice to ICANN? (actually, they even have been nice for 15 years) Why should EU be nice to UK? It's just tough negotiations where both parties try to close the bes
205.
▲
by
wsy
8y ago
Yes, you can, for personal purposes, as explained above.
206.
▲
by
wsy
8y ago
Getting investment is a very subjective business. You can play it to your advantage that different VCs have different opinions. But not if you wait for them to deliver definitions to you. The first lesson to learn as founder is that you are
207.
▲
by
wsy
8y ago
Reframing the conversation to make founders in this situation re-think their approach is very laudable, and you give very valuable and concrete advice. I still agree with the GP post that 'deserve' is an unfortunate choice of word
208.
▲
by
wsy
8y ago
Granted that sending an email implies an informal agreement. But this agreement has to be thought of as giving exactly the rights needed to facilitate the email communication, and nothing more. That means: - copyright is still with the send
209.
▲
by
wsy
8y ago
You need to get your domain concepts right, and to let your code reflect these concepts. Then, fewer bugs occur because mapping a business request to code becomes a simpler task. Also, it becomes easier to understand and fix bugs, because a
210.
▲
by
wsy
8y ago
thanks for the detailed explanation. That would at least provide a workaround.
More ›