dacracot

I asked a question but have gotten no response. Why?

1. They have moved on and haven’t made the time. 2. They disagree with my premise and are ignoring it. 3. They don’t actually understand what Claude wrote and can’t answer.

I get 1 or 2, but I’m afraid 3 is more likely. What’s more my question is not the correctness of the code, but that the method used is cheating.

The repo is a solitaire simulation where the objective is to get the highest possible winning percentage. The Claude code appears to peek at face down cards to determine which stack to play. If I’m correct, that is clearly cheating.

New PR with unconfirmed claim of 12.188%. Will review and confirm soon.

Yes, it is low, but that is the challenge to fork the repo and up the winning percentage.

All I'm gonna say is if you reduce and optimize this design, you will end up with a round about.

As an individual that attended an ivy league school, this article seems absolute nonsense as to the causality of the authors inability to bridge the class barrier. My "elite education" is not the sum total of my life experience. My encounters with other people, be it other ivy league educated or high school drop out, is a learning experience and always has been. Judging them from a class perspective is simply unwise. Judge them by what they say and their actions. Are they true to their word? Are they willing to negotiate or state succinctly what their position is? These are what human interactions are about. The elite attitude that is attributed to "elite education" more likely a lack of interaction with "lower class" individuals from early in childhood.

So why isn't this an environmental/climate change issue. These corporations that want employees that can work from home to burn fuel and emit CO2 in order to travel to the office unnecessarily should be shamed for their lack of compassion and vision. These same corporations claim to be driving toward carbon neutral while simultaneously pushing for CO2 increase via their employees travel.

The RPi foundation is anticipating their supply chain to return to normal by second quarter of 2023... https://www.raspberrypi.com/news/supply-chain-update-its-goo...

So this kind of analysis is always troublesome.

It isn't very hard to find instances of false positives when the sample size is so large. For those false positives, the cost and effort is no doubt a waste and potentially could distract from a real instance.

But what is the big picture here and the overall cost benefit? Can we find true positives where the crash victim is better off because of the alert? Are there more or less of these than the false positives? Have any of the true positives saved a life? How do you measure that? The algorithm no doubt does not have six sigma accuracy, but it that the bar that must be set before we save some lives?

As a 61 year old programmer, that knew this is what I would be doing since my first exposure as a junior in high school, I can say his insights aren't too bad. But 20 more years on, things start to hit harder. My best advice is to learn to coach, even if you aren't in a coaching role. Find that young 10x team member and teach them the subtleties of the abstractions that make a difference. Don't be offended when they rewrite your code to their way of thinking so long as it did not obfuscate the lesson, that's how they will learn.

Still doesn't suck.

Because it is awful.

Physics is simple? Can you describe to me what gravity is? Have you published your unified theory yet?

Just as a sports team wins or loses together, so too should the engineering team be treated as the fundamental unit of success.

A sports team has a play book, does your team? A sports team practices together, does your team? A sports team works as a unit, does your team?

Too many times I have see engineering teams as only a team on the org chart In reality they solve tickets as individuals with only a small interaction from pull requests. Otherwise they might as well not even know each other. They are a team not as in basketball or football, but like golf where once you get to the tee, it's you and only you to get the ball in the hole.

I get your point, but without paragraphs of explanation, I doubt I could persuade you. I can say this... It was meant as a solitary exercise, not as a group.

I'll caveat my remarks first by admitting that I nearly completely ignorant of Google's 20% policy, but since it was widely advertised, my workplace made a similar statement that one half of each Friday should be dedicated to learning something new to benefit the team and thereby our careers. All I could ever think of after this proclamation was that I was to do as I was told 85% of the time and innovate 15%. As a developer, I offended that my innovations are devalued to a time slot. I was under the impression that I was expected to innovate continuously within the confines of the deadlines given. My two cents.

Spreading your business logic across all of your code base is a bad idea in any language. Not doing it as a primary design pattern is language agnostic. Your argument has nothing to do with whether the code executes in the database, a JVM, or native to the OS.

So first I can't read the article because there is no way I'm giving them my email so they can spam me later. That having been said, what is the unit of measure? Coding is notoriously difficult to measure and the unit of measure is elusive. We all heard the problems with KLOC, function point, ticket, story, etc, etc. They are all widely variable and seldom reflect the complexity or lack there of.

First law of history... The victors get to write it.

You need to liaison differing personalities to communicate and come to consensus. First are your customers, presumably business types, to your development team, stereotypically introverted nerds. Second is the interaction amongst your team. Those introverted nerds will have opinions and you need to drawn them out to civil debate. Best case scenario in the latter is they arrive at a design themselves with you coaching, otherwise you end the debate and select for them. For the former, you need to jokingly tell the customers about the golden triangle... good, fast, cheap... pick two and only two. Then make sure they know you aren't joking any more.

I agree, and it has been going on for a very long time. I have coworkers who's productivity (if you can call it that) would slide to zero if you took away Eclipse. If it isn't implemented in an Eclipse plugin, well forget it. Setting up the deployment environment is so far outside of their capability as to be a joke. And these people have been out of college for over a decade.

* A new browser-like application will emerge which uses HTTP, but neither HTML nor Javascript as its UI construct.

* Electric cars using glass batteries will start to out sell gasoline cars.

* A product with the form factor and capabilities of current smartphones will emerge that can plug into a base and replace all be the most powerful desktop computer functionality.

* Genetically designed crops grown using ocean salt water will emerge first as animal feed and later directly to human consumption.

* Somewhere a war will be caused by the encroachment of sea level.

* The superpowers will attempt to negotiate a new Antarctic treaty in anticipation of becoming reasonably warm enough to exploit for resources.

* No manned expedition to either the Moon, nor Mars. Multiple robotic expeditions to both and perhaps the gas giants' moons.

* Polarization of American politics will take a back seat to major recession (or depression) that causes nationalization of the banking system to avoid national debt default and gives rise to talk of a Constitutional Congress, not from the progressives, but from the conservatives. The congress will fail and the United States will break up into five or more separate countries.

I worked for Redknife, later renamed OpenLatitude, that was WebVan's primary B2B exchange hub. We translated their orders/invoices/catelogs back and forth to their vendors. They were our second best customer behind MicroWarehouse.

When they went down, they took us with them. MicroWarehouse exercised a contract clause to purchase our software and hired me on a three month contract to teach them how to use it. I took it because my option was to be laid off.

Brings back memories, and not all good ones. What a wild ride.

The cycle repeats over and over. Monolith becomes unmanageable and get chopped into loosely coupled, functionally independent replaceables: mainframes to containers, application servers to micro services, etc. Drag and drop coding hits the wall and gets overrun by old languages: 4GL to C++/Java, HyperCard to Objective C, etc. The monoliths are currently numerous in the single page application realm, choose your framework. Eventually these will succumb to smaller more flexible and purposeful components.

The next question I like to ask in an interview, once they have fizzbuzz working is, "Now make it more efficient."

I came here to say this. It's not that I believe someone who is poor at grammar could not be an expert software architect, but every article makes a first impression with the title, and this one failed.

The book should be titled, "How to create a successful one-person online business."

And from a system perspective, I would wager that the cost is still higher given the complexity of their final solution.

The math is simple. This did not require a mathematician, just an cost benefit analysis.

($ * toilet each car) < shunting{($ * action * yard) + ($ * training * employee)} + ($ * accident cleanup) + ($ * customer bad will)

It's a buggy mess also.

Not necessarily... If I said MS-Word, would you decide to go out and create a word processor, probably not since the market is pretty much a done deal.