Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ircmaxell
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
12 ms
·
61.
▲
by
ircmaxell
14y ago
As someone who has worked with him for quite some time, all I can say is so very much agree. He blows me away left and right with his knowledge, ability and maturity (especially when it comes to code decisions). He's more senior than most d
62.
▲
by
ircmaxell
14y ago
The problem with that is it's already valid syntax with a different meaning. function foo($a, $b = "10", $c = "20") {} foo(1, $c=20); var_dump($c); // int(20) The syntax would have to be unambiguous. Perhaps: foo(5, c
63.
▲
by
ircmaxell
14y ago
I think composer is a bit too young to introduce into the language. Perhaps it will prove out to be robust, but I'd wait a little while before introducing it to core...
64.
▲
by
ircmaxell
14y ago
That's a very good point. I keep forgetting about hashphp... Perhaps that model is better (a semi-curated list of tutorials off site)...
65.
▲
The True Problem With PHP
(blog.ircmaxell.com)
85 points
by
ircmaxell
14y ago
|
124 comments
66.
▲
A Tale Of Open Source
(blog.ircmaxell.com)
1 points
by
ircmaxell
14y ago
|
0 comments
67.
▲
Application Architecture - The Case For Layers
(blog.ircmaxell.com)
4 points
by
ircmaxell
14y ago
|
0 comments
68.
▲
To Comment, Or Not To Comment - A Tale Of Two Stories
(blog.ircmaxell.com)
2 points
by
ircmaxell
14y ago
|
0 comments
69.
▲
Introducing PasswordLib - A Library for hashing passwords in PHP
(blog.ircmaxell.com)
6 points
by
ircmaxell
14y ago
|
0 comments
70.
▲
by
ircmaxell
14y ago
> Pretty much every PHP app in the world shares a database. So you've shifted your scaling problems from an area that programmers understand and control to a 1-MLOC mystery. True, however in my experience it's pretty easy to scale the d
71.
▲
by
ircmaxell
14y ago
My intention was the full process from creating the first file, to getting a server to serve the content is far easier to do in PHP than Python (granted, in Python it's pretty much boilerplate, but there's a lot more than needs to happen).
72.
▲
PHP Sucks But I Like It
(blog.ircmaxell.com)
326 points
by
ircmaxell
14y ago
|
232 comments
73.
▲
Understanding PHP's Internal Array Implementation
(nikic.github.com)
2 points
by
ircmaxell
15y ago
|
0 comments
74.
▲
The Power of Technical Debt
(blog.ircmaxell.com)
54 points
by
ircmaxell
15y ago
|
5 comments
75.
▲
by
ircmaxell
15y ago
A very important difference for a C developer. For a PHP developer reading C, it's a pretty good analogy that gets the point across without causing too much confusion...
76.
▲
PHP's Source Code for PHP Developers - Part 1
(blog.ircmaxell.com)
8 points
by
ircmaxell
15y ago
|
0 comments
77.
▲
by
ircmaxell
15y ago
@jakejake Wordpress uses a procedural version of the mediator pattern (just like Drupal's hooks). As I said in my post, just because an application doesn't use classes, doesn't mean it's not OOP or borrowing OOP patterns (and Drupal is act
78.
▲
by
ircmaxell
15y ago
Well, that just executes code. That doesn't alter your application flow, unless you do that during runtime at (for lack of a better word) cutpoints. And if you do it there, it's basically Chain of Responsibility, without the "chain can be
79.
▲
Handling Plugins in PHP
(blog.ircmaxell.com)
18 points
by
ircmaxell
15y ago
|
12 comments
80.
▲
Parameter Type Casting in PHP
(blog.ircmaxell.com)
1 points
by
ircmaxell
15y ago
|
0 comments
81.
▲
How We Interview Developers [ircmaxell]
(blog.ircmaxell.com)
4 points
by
ircmaxell
15y ago
|
0 comments
82.
▲
by
ircmaxell
15y ago
If that's all that your code does, then that's fine to use #1. But in a larger class, it's needlessly cluttering the class with operations below its abstraction level. Why should a logger care about file locks and the such? Why should yo
83.
▲
The MicroPHP Fallacy
(blog.ircmaxell.com)
49 points
by
ircmaxell
15y ago
|
35 comments
84.
▲
by
ircmaxell
15y ago
Thank you for the comments! My point wasn't to show how wasteful or bad rainbow tables are. My point was that brute forcing is actually significantly easier than people realize (to the point of being almost as efficient as rainbow tables
85.
▲
by
ircmaxell
15y ago
The point was that a good programmer is a good programmer regardless of their tools. And a bad programmer will always be a bad programmer no matter how much their tools do for them. Spend time becoming a good programmer, and you'll be bett