brentroose
Joined 5 years ago
Karma
423
Submissions
51
Member since
Nov 10
Joined 5 years ago
A couple of things I did:
- Cursor based pagination - Combining insert statements - Using database transactions to prevent fsync calls - Moving calculations from the database to PHP - Avoiding serialization where possible
That's why I built a performance challenge for the PHP community
The goal of this challenge is to parse 100 million rows of data with PHP, as efficiently as possible. The challenge will run for about two weeks, and at the end there are some prizes for the best entries (amongst the prize is the very sought-after PhpStorm Elephpant, of which we only have a handful left).
I hope people will have fun with it :)
Yes, we're writing less code, but the job of "a programmer" has always been about so much more than _writing_ code. It's about code reviews, QA, debugging, discovery, and maintenance; much more than the "writing" part. Anyone with production code will agree, I think: the writing part is the easy part. That's where I still very much prefer a proper IDE over a text editor or terminal. I want easy code navigation, I want proper static analysis without relying or waiting on third party tools, I want a visual overview of changes that happened. I want to stay in charge of whatever is writing my code. On top of that, I want my agents to have access to the tools that have made me the most productive developer for years.
Curious about your thoughts?