I have noticed an increase in errors here in the past few months though, I wonder if this is the cause.
4,021 karma · joined May 11, 2017
I have noticed an increase in errors here in the past few months though, I wonder if this is the cause.
Yet people die on this stretch every year, even experienced kayakers who let their guard down. What generally happens is someone falls out of their kayak / tube / whatever, and their feet get caught in a snag in the bottom. The river current is enough to force them under water.
Most places around here will no longer rent water equipment if the river is running high and fast, yet some foolish people manage to go out and die.
But not sure what the answer is for people falling in from the banks or bridges. Comprehensive fencing is expensive and ugly.
This is especially true if you consider salaries world wide vs just the United States.
“But exposure,” some folks will say. People die of exposure.
By contrast I have never been able to use Linux successfully as a desktop OS because there is a dearth of polished commercial apps, and the HW compatibility has always been iffy. MacOS generally works out of the box with the HW, and the apps are generally highly polished.
I caveat the apps as “generally” because there are some turds for sure. iTunes and now Music have always been horrible, and somehow they managed to make Music even worse than iTunes.
Historically Macs do benefit from 3rd party software (see also Alfred), over time the best of it seems to eventually get baked into the OS. I don’t see that as a downside really.
Fowler means it literally. He had examples published on Artima.com years ago where he gives examples of hard coding things left and right and adding better support “only when you absolutely need it”.
To be clear I am not arguing for big design up front. I am arguing to keep an eyeball on your roadmap, and that is not only OK to anticipate the future but maybe do some small amount of work to make the future work easier.
The fallacy of “You Ain’t Gonna Need It” is that you so very often do, and the developers down the road are cursing out the devs who ignored the future.
As it turns out, in many complex domains, you ARE going to need it, so you should factor that into your design sooner rather than later.
This is also why many consulting lead projects fail, because the developers do not understand the complexities of the domain.
Not everything is a CRUD website.
Practices like pair programming and TDD work on some instances, are absolutely terrible in others. The arrogance of the original XP folks was a hard core belief that they had found the silver bullet of software development, and then marketing it ruthlessly.
I looked at some of the small amount of publicly available code he has written, and it was frankly horrible. An example of somehow who shouts loud enough getting attention because he can shout longer than most.
The map is not the territory.
There are no physical proofs available that Christian it is right. As I say, it is all based on faith and belief.
Several other religions also have long philosophical traditions that are equally plausible - or not - and for which no physical proof exists.
As it turns out our district overall state test were abysmally low.
The net result is general flight from the public system, either via home schooling, “Choice” programs that let you go to other districts if yours is inadequate, or private school. Graphing our school enrollment numbers has gone from about 970 students in district in 2017 to 670 in 2023.
Coupled with the increasingly common practice of grade inflation, kids are hitting college woefully unprepared.
The best decision my wife and I have made in our lives was to get our kids into private school 18 months ago. The difference is like night and day.
It is very simple. If you move your data off cloud provider X, cloud provider X is losing revenue because you are doing things with your data off their platform.
They therefore charge high fees to move your data off the platform to discourage this behavior. Meaning you now need to use cloud provider X’s services to do anything with the data.
Attempts at vendor lock-in have been core to software service companies since they were born.
This is why egress is dirt cheap on other platforms outside the big 3 cloud providers.
This is also why ingress is free.
The charge is not based on cost in the case of the big names. They charge an arm and a leg because they want to keep you and your data on their platform. When you move it you are breaking free.
Hence the high costs to deter this behavior.
The situation seems to be much, much worse now 12 years later from what I have read.
When I am in a period when I am reading books regularly, I am generally happy. Things are going well, I have good life balance.
When I go a stretch without reading books, I am generally stressed out and in burnout mode at work, and home life is not great.
Note - this is generally fiction. I read very little non fiction.
Note 2 - most people I know have no books in evidence in their homes. Maybe they read Kindle or other ebooks? But I think many simply do not read recreationally.
But you are totally right it can be expensive. I worked with a startup that had some inefficient queries, normally it would matter, but with RDS it cost $3,000 a month for a tiny user base and not that much data (millions of rows at most).
In the kitchen sink model all teams are tied together for performance and scalability, and some bad apple applications can ruin the party for everyone.
Seen this countless times doing due diligence on startups. The universal kitchen sink DB is almost always one of the major tech debt items.
Fortunately, with managed DBs like RDS it is really easy to run individual DB clusters per major app.
In theory, the idea that "people can specialise where appropriate without having to understand the whole thing" sounds good. In reality, so many, many, many bugs and piles of technical debt pile up from developers with a worms eye view who don't understand how the whole system works. Eventually you have to make this compromise, but resist it as much as you reasonably can, and always strive to grow developers so they know as much of the system as they possibly can.