2,971 karma · joined February 23, 2019
I tried reading about Kubernetes. Holyshit what a monster we've created. I am sure there is going to be an orchestrator abstraction for multiple Kubernetes clusters. And then we have environment variables, secrets, access keys, a bazillion different parameters that need to trickle down from Gitlab CI settings all the way to the app through many layers.
Good lord. All engineers should be ashamed of this mess. We've forgotten how to build simple, beautiful, lean and parsimonious software. Instead of writing logic, I am configurating things all day.
Let there be a day where there is some deep compiler problem and this entire house of cards comes crashing down because your DevOps team ain't gonna know what happened down in lower abstraction layers. But, let's shit on the F-35 program everytime there is a Lockheed article on HN. Because surely, software engineers are the smart bunch ya. I know, I am unreasonably obtuse here, but jeez, no one complains about today's deployment process,... its apparently accepted without a question.
Yeah I agree, if you end the sentence abruptly it sounds blunt. Just replace it with "Please pick up milk on the way home" and it sounds normal. But that's not what I said.
I can't believe we all have spent so much energy, downvotes, and bikeshedding including myself. This is surely not efficient. Instigator is the offendee. What a disgrace!
I feel the complete opposite. I structure projects, not my time. I want a loose schedule. You could stop worry about time, try a free schedule, enjoy life a little, and get work done. This whole "productivity" bullshit is an urban concept. Back when my grand pa was a farmer, he didn't have a schedule but he worked all day. The task can take as long it has to. I am willing to bet, your average urban wizbang with TODO apps and productivity hacks will not match the output.
Tangentially: Same thing happens in code reviews. People become extra soft at objective reasoning!!! The onus is on the offendee, not the offender. Stop being offended so much all the time, you'll live a healthier, happier life. Special treatment, feeling of being entitled for politeness is a slipper slope where everyone is being nice to each other and no one can criticize. Nothing gets done. We don't make progress together like this.
Advice to the sender: Be polite, but assertive. Don't make personal attacks.
Advice to the receiver: Assume good intentions, focus on problem at the hand, accept harsh criticism, don't be offended at little things.
The world would be a better place.
Think more abstractly. A business is delivering piece of IP to the customer in exchange for monetary value. The medium of this IP can be physical or intangible. It is the delivery latency that's different. If those screws that I talked about arrived in about 45ms latency from the warehouse to the customer, and fitted themselves in another 2mins, you could patch things instantly. Just because this latency is different, doesn't mean you ship MVPs, broken pieces of software that require constant patching. Take time, carefully think about the architecture of the software, think about extensibility and modularity. Avoid feature creep, instead work on just works aspect of the product. This is why I love software from companies like Sublime HQ. They make fast, efficient, well architected software that's a pleasure to use. Similarly, there is something beautiful about unix utilities, little pieces of software that just work :) Continuous delivery is great for huge software, Arch Linux, for example.
I recommend watching this incredible talk (it's about software) : https://www.youtube.com/watch?v=pW-SOdj4Kkk
I wasn’t talking about mere resemblance. I’m talking about functionality, density of information, layout, hierarchy of importance exemplified by various aspects of the UI, clarity and intent, feedback and signaling, on and on. The whole thing. The only thing that bothered me about SAP was how clunky it felt, simply because it was slow.
I’ll quote myself: “It is dense, extremely clear and consice.”, yep it’s great to use. I also love JMP statistical software UI and Cinema4D UI. They’re a pleasure to use.
Contemporary UI trends bother me except one: websites like drewdevault.com and text.npr.com are refreshing.
It is dense, extremely clear and consice. I agree with the slowness though.
We need to stop being offended so damn much. The society is getting softer and more punishing to unintentional offenses.
Edit: LOL @ the superhero comment
That's self-contradicting. If Traffic is chaotic, then people are either not cooperative or the rules are set but no one is following. If the rules are well architected, enforced and obeyed, then the traffic wouldn't be chaotic.
What GP is saying makes sense to me - traffic sense tells a lot about the society. It exemplifies that developing nations have tough conditions, out of control population, limited resources and stiff competition; if you're a nice guy, you'll lose. I am sure many people in Mumbai would like to cooperate, but they are held back because of the aforementioned trap.
Also, wouldn't this cause issues with the general flow of the traffic? One delay and you have cascading effects that perturbe macroscopic traffic patterns at the city level.
This type of punishment would be detrimental in well coordinated traffic (probably not Mumbai): Study of traffic is an entire field in scientific research, https://en.wikipedia.org/wiki/Traffic_simulation
Let's not pretend Facebook is an impartial processor of information... They are absolutely not. They're arbitrators of information. They sell information for a profit at the expense of privacy. At the expense of societal good. Google, Microsoft, Adobe, Viocom, etc. not just Facebook.
Regarding the hyperbole - yep, I realize that. I am here to express my opinions, emotions and speak freely; not to tread political correctness and wimp out on calling things as they are.
I wonder if Mark Zuckerberg ever sits down, brew some tea and question ruthlessly what his purpose in life is.
"What do I want to be remembered as? As a guy that has ruined America, the world in some ways and spreaded false news, kowtow to the advertisers, chasing year over year profits, quarter over quarter revenues, created echo chambers, fucked up politics, sucked up to investors?"
RED - Actually red (unlike Google Maps)... its bumper to bumper or less than 5 mph (8 kph)
ORANGE - Slow moving, perhaps less than (25 mph or 40 kph)
Google just shows everything RED. Yellow doesn't necessarily mean slow down in Google Maps. Its a mess.
Also, Apple maps is tremendously accurate in estimating how long it is going to take.
Major feature missing in Apple maps: Time it takes at a user specified hour. I use this to hunt for apartments, and test out how long it is going to take to and from work everyday. Google has this built in for a while "Leave at ____ time).
The core developers are of Julia are very smart folks, they want to develop a great language that's fast and easy to use. They missed the opportunity to restrict syntax, provide useful exception message (just look at Rust! it is a thing of art when you get an exception, it is beautiful), and generally provide good documentation.
For example, just creating a Julia local registry requires significant overhead and time investment. Spinning up a registry should not take more than 30 mins.
All these aspects of Julia are prohibitive and in my opinion, Julia should not be used in any company or production use until perhaps version 2. People who have dealt with Julia issues will tell you the truth - not the academicians or researchers. The people that maintain infrastructure/maintenance support for Julia apps are almost ready to quit their jobs. It sucks so bad.
Debugger support is almost non-existent. Using Atom/Juno IDE is a D-grade experience. Julia offers little help to debug problems - errors are almost always without failure - completely tangent to what the real issue is.
Julia takes forever to start, syntax was wonderful pre 0.4 days, now the syntax just looks absolutely jarring to my eyes. Julia's speedups can be offset by using many many far better technologies - Numba, Numpy, Cython, PyPy etc.
Julia's ecosystem of libraries is a deserted land - that's expected for a new language. I hope it improves, but the core Julia experience needs to improve first.
On the other hand, I've been following Rust development and the developers made absolutely sure from the get-go to focus on debugging/errors that show what the actual problem is, provide a stack trace and figure out where the problem started. Julia absolutely sucks at this.
Another example is Library of Congress logo designed by C&G, timeless until it lasted and Paula Sher(Pentagram) destroyed it. https://www.underconsideration.com/brandnew/archives/new_log...