That said, I am not a huge fan of fluent interfaces. I much prefer passing in a struct as an "args" parameter, in most case (but not all.)
39 karma · joined June 20, 2009
That said, I am not a huge fan of fluent interfaces. I much prefer passing in a struct as an "args" parameter, in most case (but not all.)
So using these functions is becoming part of what good Go programmers do.
But then I am super zealous about making sure my error messages understandable without the need to track down other information. For example, I want to know that (something like) "the config file needs group read permissions" not "file cannot be opened." But maybe others value ease of programming more than I do and are less concerned about error UX than I am?
Also, what editor/IDE do you use? The reason I ask is because of this: https://youtrack.jetbrains.com/issue/GO-7747
It might be fair to say the ergonomics are suboptimal for the code _writer_, but I would say they are much closer to optimal for the code _reader_.
> I would be very concerned to see a developer using the debugger on a daily basis especially if they're using it for state validation.
Those two statements seem to be in conflict.
Or maybe I should say that latter is not "policing" so much as "patronizing" in a condescending manner.
I have long thought if I was unable to use a good IDE debugger I would just change careers. Why? Because often I make the wrong assumption about the data that library or 3rd party functions will return. It is not until I can actually see the data that I realize my assumptions were wrong.
Using a debugger is all about learning, and debuggers make learning faster.
I am often able to code rings around my peers on projects. And I believe the reason is not because I am better or smarter but because I use a good IDE and debugger. And they don't.
One of the bigger blindspots I find with exceptionally bright people is they have no concept of how their brains are capable of things that far exceed the capabilities of the average person.
Or said another way, of course Brian W. Kernighan and Rob Pike think that thinking harder is better than experiencing and seeing. Because they can.
#jmtcw
This reminds of of the old saw "Those who ignore history are doomed to repeat it."
If you are unaware of the benefits, here are a just few links that can explain it:
- https://www.quora.com/What-are-the-advantages-of-REST-over-a...
- https://www.quora.com/What-is-the-difference-between-REST-an...
- http://duncan-cragg.org/blog/post/getting-data-rest-dialogue...
- https://apihandyman.io/do-you-really-know-why-you-prefer-res...
- https://www.quora.com/What-are-the-pros-and-cons-of-REST-ver...
http://www.quickanddirtytips.com/education/grammar/what-is-a...
Why is their use of Laravel's code not applauded instead of being derided?
Further, many years development experience has allowed me to appreciate that the benefits of a programming language are often inversely proportional to it's level of design purity. And the greater the longevity of a widely-useful programming language, the more haters it will have.
That's FUD. WordPress is not hard to secure if you follow some best practices and do not use crap plugins.
That said, one would hope with the projects budgets that big businesses offer to agencies that agencies would hire competent people to build their sites.
Full disclosure: that's what we do; build WP sites for agencies on behalf their big business clients.