Great game!
295 karma · joined March 24, 2016
Great game!
I made a service that was reliable, but only because there are a lot of ifs inside the code that fixed bugs. It was really shitty code that somehow worked reliably.
The service was replaced because someone else rewrote the whole thing in another language.
Is it experience? You have to review the tasks periodically? You use some kind of metric?
Sometimes I think I'm too slow, and sometimes I'm too overwhelmed and I only acknowledge it after some non-trivial time passes (or, at least, that is my perception).
doc-comments are good because it explains well what the class/method/whatever are there for, sometimes with examples, that helps understand the code.
But I hate that they use so much space inside the source code that I have to scroll hundreds of lines to read the code. And those doc-comments are filled with markup that makes it harder to read.
I would like a literate a system that generates source code that is well formatted and where the only comments are what the function does and some inner function comment where the code is complex. Every other lengthy and detailed description should be inside the produced pdf/html.
AFAIK, there are some types of notebooks that allow the use of chunks, but I've never seen people writing in those.
As an engineer, it's hard leave some things half baked, but it is what it is.
I'm thinking o using blazor server in a production app, but the latency and higher costs may be a problem. Wasm is not ideal for me because of the high initial payload.
You may probably tell what went in hindsight, but even then, it's just one if in the lifetime of the project.
"Oh, we could've released when x was done". Maybe, but maybe not too.
// Receives n >= 0 and returns the n'th fibonacci number
int fib(int n) {
// We use the memoized version of the algorithm.
}It's so easy that people can use thousands of machines to handle the load. This with the "hardware is cheap, dev time is expensive", makes it common to see those kind of very large systems.
"Programmers waste enormous amounts of time thinking about, or worrying about, the speed of noncritical parts of their programs, and these attempts at efficiency actually have a strong negative impact when debugging and maintenance are considered. We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil. Yet we should not pass up our opportunities in that critical 3%."
From some readings of Knuth, I have a feeling that he always think about efficient code.
k8s is a blessing because you can scale out easily and is a curse because you can scale out easily.
People who think the bottom line is zero don't know how to read a chart.
What maybe is missing is a table with the statistics to compare numbers with maybe a latency number.
Once they're hooked on, they'll have to learn the details. I don't know if you're old enough, but Rails got a nice momentum with their 'Blog in 15 minutes'.
Of course your senior engineer that wrote the thing will be more productive than your intern that writes 1000 WPM.
Imagine that you want to correct a block of code or a whole paragraph. If you don't touch type, maybe you will think twice before rewriting it.
It means that's easy to talk about a finished work, it's faults, how it could've been done better and, if one were to replicate it, he would take a lot of less time.
Of course he would, someone else took the trouble to plan everything and fix the all the problems to reach a reasonable architecture/design. And obviously, that person will never do it because "it's trivial".
Columnar databases are a good fit here.
You should read the title as "Design Patterns for Java". You can try to implement the patterns in other languages and it may work but, if it doesn't, that doesn't mean the book is useless, it just doesn't fit your language of choice.
I believe someone would've written a book similar to "Design Patterns" at some point in time. It just happened to be the GoF.
You can say whatever you want, but today we all use patterns to talk about software. It may or may not be thanks to the book. We'll never know.
I thought the same in the past. But I think it's a good idea to enforce word limits to make them think more about the subject and to practice writing longer and complex texts.
The problem is that the teachers just impose a limit without explaining and then it just looks like some bullshit metric.
I think modern journalism is more about SEO and getting attention, not word limits imposed when we were in school (if you hate word limits, then you probably dind't continue writing longer texts)
Not inserting bad data is much better than trying to make sense of inconsistent data because you don't know what is true or not.
The author could have just kept "Taming Go's Memory Usage".
Maybe they never considered rewriting in rust. The pros and cons looks like just some random arguments to add rust to the title.
The search engine and the ads are tightly coupled. A better search engine means it can predict with more accuracy what you are looking for and can serve you an even more targeted ad that increases the chance you'll click.