temporama1
temporama1 on Hacker News
I see tests like this all the time:
// TestConstructor
Object o = new Object();
assertNotNull(o);
Completely bonkers, but mention it and people just look at you blankly: "....but the test coverage".
Cult-like thinking.
Counterpoint to this: a lot of the programmers I admire all have an uncanny ability to just sit and work for long periods of time. Like, sit down and hardly move for 10 straight hours. They achieve a huge amount in that time - much more in a single 10 hour stretch than they would in 10x1 hour sessions.
And that applies to other things they do: playing video games, reading a book...when they do something they go 'all in'.
I feel like this level of focus is much more of a superpower than small amounts every day (although that too is powerful, and both approaches are infinitely better than what most of us do, which is very little)
Any tips on how to change the timestamp on your Git commits? That way you could get your work done on a Monday and spread the commits out throughout the week. I've looked at this before but there are two timestamps on each commit (can't remember now what each of them denotes) and I could only change one of them.
Whatever we do, please do not solve the actual root issue under any circumstances. That will not do. We need to stick another layer on top of the pile so we can have conferences and hashtags about it.
There will have to be something to solve all the problems that are created by Kubernetes, which itself exists to solve the problems with Docker, which exists to solve the problems with VMs, which exist to solve the problems with Operating Systems.
I can't wait for the next layer of complexity to be added. It will no doubt be called something like WizzlyBobATron.
> I'll come up with my own tools. They won't be great, but...
They WILL be great. They'll do exactly what YOU need them to do, and nothing else.
Software at present is a disaster, partly because we're just piling on complexity all the time, thinking only of the benefits and never of the huge downsides ("fighting with tools").
Any independent review would inevitably be done by the same type of "expert" that wrote the software in the first place.
No doubt it's some sprawling, insane Java monstrosity Manhattan project or suchlike.
"Yeah - 10,000 classes - completely fine and not crazy at all."
As: a postmaster
When: I use this software
Then: I should not be falsely imprisoned for 3 years.
Dude, I'm so jealous that you haven't even heard of DevOps. I don't know where you must work but please give me a job.
- Take CS50
- Take Nand2Tetris
- Take Casey Muratori's upcoming course StarCode Galaxy.
- Get some inspiration from Jonathan Blow and Casey Muratori on YouTube, and start the rabbit hole there.
- Be prepared to question a lot of the dogma that you have already absorbed.
He's probably created an anonymous account because we live in a world where you may well lose your job for even questioning that a _source control branch name_ might offend someone.
An opinion that - in the real world - the vast majority agree with.
Nobody had a problem with "master" 18 months ago. Including you.
Bitkeeper must be punished for these transgressions.
The number of people that _genuinely_ have a problem with the word "master" (excluding all the weird (white) twitter people) is close to zero.
> My phone is that internet/phone addiction is not a problem its a solution
Funny that you've mistyped "phone" instead of "theory".
Must be a Freudian phone.
Go low level. Get back to basics - abandon higher level abstractions (thinking bloated and depressing frameworks). Implement a project that interests you, purely for fun.
If the US disarmed and Iran, China and Russia were in charge, do you think the world would be better or worse?
Association of Tennis Professionals
JavaScript is not the problem.
Computers are AMAZINGLY fast, EVEN running JavaScript. Most of us have forgotten how fast computers actually are.
The problem is classes calling functions calling functions calling libraries calling libraries.....etc etc
Just look at the depth of a typical stack trace when an error is thrown. It's crazy. This problem is not specific to JavaScript. Just look at your average Spring Boot webapp - hundreds of thousands of lines of code, often to do very simple things.
It's possible to program sanely, and have your program run very fast. Even in JavaScript.
> the downside of adding more features is that it becomes increasingly time intensive to fix bugs, update demos, deal with pull requests and respond to questions.
Thibaut Duplessis, creator of Lichess, talks about this in a talk he gave (YouTube somewhere). He says that he's very reluctant to add new features due to the huge cost. The feature must be something very special to overcome the cost.
Good one. Nearly had me for a moment.