Can we collectively refrain from making comments like this on Hacker News—or in any venue, for that matter? Is it that hard to read an assumed “In my experience, it is often the case that…” in front of everyone’s comment?
The care and thought you put into your writing, regardless of medium, says everything about how (and how much) you care and are thinking about your audience.
When I think of royalty free music for “creators,” my mind instantly goes to the sort of cliched, bombastic audio that is used to score “epic b-roll” that serves no purpose in so many YouTube videos. The world needs less of this, not more.
I don’t know about you, but reading that first paragraph of the organic chemistry textbook was not a drag. It may not have been Carl Sagan’s Cosmos but I don’t understand how any generally curious person wouldn’t find it interesting. For the record I never took anything beyond Chemistry I in college.
I wanted a monochrome terminal but was willing to tolerate traditional ANSI color. Once you start with 24 bit color you may as well start using a VNC client.
What sapped my will to live was the impossibility of doing a C-u C-x = on the overlays to determine how their contents were styled, forcing me to go into the source code of a ton of different packages to go fishing for face names to coerce to visible values.
Yes it’s possible but it’s insane. Emacs carries around all of this terminal baggage but many module developers seem to have forgotten about terminal users. Additionally, theming is conceptually broken in that it creates an MxN problem with themes and modes’ face names. This could be solved if modes stopped with the proliferation of mode-specific face names but good luck with that.
I basically gave up on Emacs and switched to a combination of VS Code and old-school vi for Go and everything else, respectively. Finding an effing theme that allowed me to program in Go in a terminal without making LSP’s overlays unreadable was nearly impossible. I spent days trying to make this work. I’ve used Emacs since 1991.
Upon reading it my thoughts went to yesterday's Verge article on the audio recordings of Zuckerberg's Q&As. Facebook has many vocal rank and file people who seem to believe they've arrived at Enlightenment and want Zuckerberg to toe the line. His imperfect attempts to walk a tightrope that keeps everyone happy infuriate the Enlightened, who believe tightrope walking is in its very conception a concession to Evil. They conclude that he's an Agent of Hatred and start taking steps to coerce him into compliance with Correct Thinking.
ICX Media | Golang/Python GCP Data Engineer| DC, NY, SF, LA | REMOTE
ICX Media is helping organizations gain insight into online audiences and act on those insights. Key to achieving that goal, ICX is building a world-class data practice, and we’re looking for people to help us achieve our ambitious goals. We have embraced Google Cloud Platform (GCP) and are building atop it batch and streaming workflows using Dataflow (Apache Beam), Cloud Run, and BigQuery, orchestrated using Cloud Composer (Apache Airflow).
Our preferred languages are Python and Golang. We highly value data science as well as relational modeling and SQL knowledge, skills, and experience. If you’re an engineer that wants to concentrate in data engineering or a data scientist that is interested in making a move to the engineering side, this may be a great opportunity for you.
The ICX data engineering team has embraced a remote-first approach to working and has members that span Eastern to Pacific time zones. This opportunity is open to US citizens and others authorized to work in the United States.
Contact me at work my email ([email protected]) and please reference this post.
The claimed "plausible deniability" benefit seems dubious. You are carrying a branded device with marketing materials that tout its ability to offer you plausibly deniability…
SO is the opposite of MDN. If you do not approach any piece of StackOverflow content with the presumption that it could be dangerously not-even-wrong, God bless you.
Assembly code making poor choices can be outperformed by Python code making smart algorithmic choices. The sentiment behind "don't use Python for performance critical code" isn't wrong, but there's nuance. Programmers should make informed choices about space and time complexity regardless of the language being used.
Your typical assembly programmer may be far more aware of their obligation to do so than your typical Python programmer, so in my mind it's more important that languages occupying Python's ecological niche behave predictably. It can be challenging to balance that need against other constraints like limiting the number of abstractions someone needs to master in order to be productive.
Both your and the parent's sentiments are so on-point. And they're one of the reasons I don't like ORMs or the use of in-app constraint checking. The mid-Aughties rise of CRUD-focused frameworks that treat the database as a sidecar to the web app ignored as inconvenient the full power of an RDBMS, in part because MySQL was the not-full-RDBMS that they were often paired with.
It's not necessarily about money. An engineer can burn through tens of thousands of dollars per month in cloud spend because they have access to the AWS [or] GCP console, but that same engineer may not have the first idea about how to get the CFO's sign-off to purchase a license that will facilitate a halving of that spend. And that same CFO can institute a policy against using credit cards for recurring payments that prevent that engineer from expensing the purchase through a corporate card. And the software company may not offer a bill-via-invoice option — or they may only offer it for amounts greater than the amount the engineer wants to spend.
So much of what happens in sufficiently large organizations has nothing to do with profit maximization. Think confederacy of dunces, not a conspiracy of greedy evil geniuses.