You can replace a derailleur hanger on a modern bicycle for about $10 or less. This is the part that bends on a right-side crash.
108 karma · joined September 1, 2015
This is just how it goes. No matter how much we wanted him to stay, there was nothing to be done about it at our level.
Managing your depression will always be part of the trip. Don't listen to the voice(s) that say you are a failure/loser/underperformer, just do your best. Say it to yourself whenever you need to: "I'm doing my best, and that's how it will always be."
Strangely, when I know that I'm doing my best despite everything, I feel calm.
Text is indistinguishable from print type. You're able to see an enormous amount of information without panning. With a good mouse you can pick and rubber-band much larger groups.
Some people think you can just write software, sell it to customers, and it's "tuning" to make it work properly.
You should be fired from whatever job you have.
My guess is that you have no job, you are fronting USD.
In which case you have absolutely no place in this conversation and you should be ashamed of yourself for speaking up.
A fool and his money are easily parted.
Otherwise known as re-architecting?
That doesn't prevent us from thinking about performance. GTFO with this nonsense.
I have no patience for persons who don't belong to the discipline.
What the f*? Of course it would have been easier if you had done it sooner. What you lacked was the willpower from decision-makers who had growth of dollar-signs in their eyes.
You've littered this thread with comments explaining how every move you made was based on ROI. That's the kiss of death for architecture concerns, and bizarrely it puts Node.js on the list of runtimes for data/stream processing backends.
No matter how many times you explain how you made these decisions, I can't help getting the feeling you were wearing horse blinders.
Edit: I find it impossible to imagine that nobody on the engineering team ever shouted, Hey look out! We are basically a Web farm for banking-related requests, this is insane! Surely you've heard from those people and they were let go.
Hire an architect costs what? Putting the genie back in the bottle was a problem Plaid baked into its early success, which is common with startups hiring engineers with zero architecture knowledge.
I don't know why, but most people are not aware of kneeling chairs or the benefits they provide to back posture. There is literally no way to get healthy curvature in a sitting posture without lowering your knees below your hips.
Nobody said making the leap to distributed systems architecture would be easy. In fact, quite the opposite has been alerted, over and over.
Do not complain about complexity and simultaneously reach for hard problems.
Edit: In most meetings I feel neutral and disaffected.
I guess around the time Sundar became ascendant.
I had no difficulty with long-running jobs because servicing jobs out of PG was simply a matter of pushing them onto the Kafka queue for immediate uptake there.
On my first go I was taking batches, on the reasoning that it optimized for query performance. It was a complete disaster and I quickly realized that I was engaging in premature optimization.
Batching is out, stream-processing is in. If you design your job table correctly, PG will perform very well as an advanced stream processor.
A corollary reason is to improve your "mechanical sympathy" when writing high-performance code.
Many of what we once called "application devs" -- now more commonly "full-stack devs" -- will never have to discover real mechanical sympathy, which is fine. But there is a glass floor for such people.
It's a great solution.
I think you mean either "wary" or "leery" but not both at the same time!
Newbies of every stripe are encouraged to think that language is the entry point for software development, but it's a teaching moment that most teachers fail. The language is not important.
The runtime is important.
Newcomers don't need connectors anyway, they need the room to experiment with syntax and such, get their head around ASCII symbols. It's great, good luck.
In my teens I wrote Snake and Dig-Dug and Chinese Checkers and whatnot. I was learning to write anything at all. But twenty years on, distributed systems are applications. Writing Golang as though it changes the paradigm is fucking silly. But learn however you want to learn.
If you thought using a new language would give you better runtime character, you were wrong. Languages are transpiled and cross-compiled on the reg, and it really makes no difference to the runtime what language you used to get your bytecodez into the scheduler.
And frustrated that I'm not hearing anything from Golang programmers about how it enables a larger class of software.
"We're writing the same software, just better" isn't a reason to come up with a new language.