commentnull

Chrome changing the rules again? Unpossible! Still, the good news is that people are leaving chrome for ff, safari, new ie, so soon, it will be less of a problem. Hurrah!

This is the kind of stuff you want running in a service out side of a micro kernel, but as we are stuck with systemd/gnu/linux systems, this is what we have...

Depends - are we hiring brogrammers or precious snowflake developers who must be feted and every desire fulfilled to keep them happy - and let them keep producing the crap bogging down the web as we know it?

The Simpsons and HN have a lot in common - both still feasting on previous glories, both past their sale by date, both not even realising how tragic they have now become.

Yep. Chrome had its moment in the sun, helped push some vital changes in the web ecosystem in its day, but now it has become a parody browser. When it is not crashing it is a fragile thing that seems to break every page, despite the fact all the web gurus try to optimise for it. And how much system resource does it want? Makes me miss simple browsers like Dillo.

So, the end user of the site has no say? They should be thankful they are even allowed to cast their eyes on such a technical masterpiece? Developer or not, people can spot a worrying trend of website "developers" who cannot develop - they just bolt bits and frameworks together without a consideration for the end users.

It is an awful experience. Mobile data is often sketchy, but these bloated sites don't render a single thing until all the twenty tons of front end crap is downloaded, and all to view a tiny static chunk of text. But hey, they got to use react, a metric shit ton of the latest CSS wankery, and it is connected to every social meejia platform!

Because the modern "developers" don't know how to do so. They barely manage to bolt together a backend that scaffolded everything magically for them, to react, less, and other "magic" they followed pavlovian style from blog postings.

My name is not Richard, or any abbreviations of it! But yes, I do actually know people who have have to have subsequent ops, where material was found from an earlier op. Not as uncommon as you would think, sadly.

It's true - the professor awarded everyone who turned up to class that day fifty percent, just for turning up! One student then started to question that decision - the professor said "aha - critical reasoning! Very good, extra marks for you!". Another then said they would write to the dean to complain, the professor said "excellent, I will award even more marks to you in anticipation of your written effort".

Seems like getting the grade got too easy...

I liked where he had to track down one patient because he had left the keys to the summer condo inside after they fell in during the operation! Makes you think...

Writing a good technical book is hard work with uncertain rewards, and the very real possibilities for loss for those involved, so how do some publishers seem to be able to have so many titles? Is the model reliant on a few bestsellers to keep the rest going? Would love to know how it really works...

In the meantime, I still love these books, still buy them (I have this one), and hope they don't go away.

I preferred the 'Pattern' pattern, where each line of code is its own pattern. In fact, I think he writing a whole new book about it now.

I have just bought a "Learning GROWS" book from the Pragmatic Programmer online store, and have hired a consultant to educate (inculcate?) the team on the new methodology.

We even are using one of the new open source libraries that tests and enforces the process, it is called 'poison ivy' - it hurts, like all good software engineering processes do!

Edit: do the downvoters disagree? We don't think there will be books, courses, tools for this new methodology?

Code reuse is great, unless it is Qemu?

The article starts with the current note - agile as it was preached was never actually achieved, and most companies and practioners are doing it "wrong" (for varying degrees of wrong).

But then it goes downhill with proposing yet another model that will people will try to adopt verbatim, and again, experience failure to implement.

Software is hard, people are hard, so the idea should be to have as little process as possible. Most of it exists as arse-covering material anyway.

What really killed agile fwiw, where the consultants, going from development team to team, peddling false hope, snake oil, and tedious time zapping process that people learnt to game rather than actually deliver.

Of course, someone will pop up saying agile is awesome, they love the daily scrums, the project is fab, the sky is blue, etc. Question is: can it be better?

The faux crowdrage these days is depressing. I suppose it is the modern version of the crowd gathering to watch a stoning, hanging or other public spectacle from the middle ages.

Someone made the point yesterday, a good point I think, that the Go and Rust crowd would be better served by showing positive blogs and examples (i.e. Here is how to build a small app) rather than ones that serve only to whine and complain and bemoan C/C++.

You don't win friends by criticism.

As a seasoned C++ programmer, I am interested in Go and Rust, but not because a few ardent posters told me I have to.