hhas01

45 ms·

361.
by hhas01 7y ago
Expect Shortcuts to land in 10.16. Most of the plumbing’s already in 10.15; it’s just not public yet. https://twitter.com/stroughtonsmith/status/11359563313603461...
362.
by hhas01 7y ago
“They use API's to order pizzas, hail Ubers, subscribe to YouTube channels, update parameters for Netflix recommendations, and do lots of other things that have real-world side-effects.” That’s three POSTs and a PUT, with the appropria
363.
by hhas01 7y ago
Or you could learn how to build REST-ful web interfaces correctly, in which case the problem goes away. The only #SeparationOfConcerns that actually matters is: 1. Verbs describe actions upon resources (e.g. add, read, delete) 2. URIs
364.
by hhas01 7y ago
Know how to design a RESTful interface correctly, and you don’t need “API versioning”. Certainly not URL-based versioning, which is as anti-REST as it gets. The correct way to manage non-backwards-compatible changes in a RESTful system is t
365.
by hhas01 7y ago
Article has nothing to do with “REST”. Thankfully so, because 110% of what is written about “REST APIs” is an absolute bag of shit. #OxyMoron
366.
by hhas01 7y ago
Liberal ≠ Malformed; an atrociously common misconception amongst atrociously common code. The modern Web is the product of people who have so deeply and comprehensively misinterpreted and misunderstood every single facet that they are Not E
367.
by hhas01 7y ago
AppleScript’s reckoning will come once Siri Shortcuts officially ships in macOS 10.16. As Steve Troughton-Smith has demonstrated, the technical guts are already present in 10.15 [1]; it’s just not quite ready to roll as a Product yet. [1]
368.
by hhas01 7y ago
Don’t be daft. If the Homebrew team aren’t already busting ass to rewrite brew in Objective-C, and negotiating to get it distributed on AppStore or—ideally—included in Xcode as standard, then they’ll have no-one but themselves to blame wh
369.
by hhas01 7y ago
Amusingly enough, 10.15 is the first and last macOS to ship with python3 bundled as standard. As to the rest of it, I’ll just re-post the same comment I post every time some muppet starts with all the wailing and rending of teeth: This is
370.
by hhas01 7y ago
How the Boeing 737 Max Disaster Looks to a Software Developer “Ehhh, we’ll patch it in the next release…”? /badum-tish (Actually a really deep and insightful read. Tx.)
371.
by hhas01 7y ago
Liar. Fuck off. https://sciencebasedmedicine.org/?s=wakefield
372.
by hhas01 7y ago
Good question, and I think it reveals an embarrassing truth about common hiring practices: they’re designed to test for qualities that can be trivially tested for, rather than qualities that are actually productive down on the shop floor. I
373.
by hhas01 7y ago
In order to better solve what business problem, exactly? If I was your boss, I’d demand to know your projected ROI calculations up-front too. That includes the near-term risks and costs of change management when phasing in your new technolo
374.
by hhas01 7y ago
And no doubt many more companies being more unsuccessful using PHP too. If you really must go comparing apples to pears, a marginally less worthless metric might be the percentage of each that has worms in.
375.
by hhas01 7y ago
Indeed. Pick the right tool for the job. Picking the tool just because it gets you lots of cheap disposable developers simply means you end up with lots of cheap disposable code. Good for the current quarter’s C-suite bonuses, no doubt; may
376.
by hhas01 7y ago
Just something I stumbled on while rummaging around: https://tryapl.org/
377.
by hhas01 7y ago
“Both were wildly frustrating to work with because the real knowledge was all tribal” I suppose it depends on what you mean by “tribal”. A good DSL is naturally tribal: it serves a very specific user base in a very specific field. If you
378.
by hhas01 7y ago
True dat, but what does “must have 20 years’ experience with $technology” even mean? Using it day-in, day-out, for the last 20 years? Originally learning it 20 years ago, and periodically brushing up on the current release every few years w
379.
by hhas01 7y ago
Of all the reasons to say “no” to a job at Crapita (see Eyes passim), having to pick up a custom language sounds like the least of them. Though considering payroll’s one of the oldest and most solved problems in software development (Hi, LE
380.
by hhas01 7y ago
I think the key to understanding APL is realizing that it’s not built for Programmers; it’s built for Mathematicians. Here’s a fine half-hour introduction to APL in action: https://youtu.be/_DTpQ4Kk2wA 1:00-2:00 is the moti
381.
by hhas01 7y ago
“I knew the knowledge was not transferable.” All knowledge is disposable. What’s transferable is the ability to learn , along with the deeper insights and understanding of the problem space which its practice brings. Pathological packrat
382.
by hhas01 7y ago
“I have seen two similar “company-specific” languages in my relatively short career” Seen them? Hell, I write them. “The commonality to any language used primarily in a single industry is that it is dead on arrival. As soon as the original
383.
by hhas01 7y ago
Related: http://lambda-the-ultimate.org/node/5569
384.
by hhas01 7y ago
LOL, obvious #MagicalPixieDust peddler is obvious. Real AI is currently three-to-eight years away, just as it has been for the last 40 years. They shoulda just said it uses “computers”. In the meantime, you know what does work here and no
385.
by hhas01 7y ago
Currently I’m in Language Design Hell trying to devise a syntax that is as easy to speak as it is to type, but if/when I get that cracked I’ll take a look as this looks very relevant to my interests. (Related: https://news.y
386.
by hhas01 7y ago
Honestly, “Why?” is the first , not last, question you need to answer, not least to help clarify your own thinking and nail down your end-goals. Who’s its market, and what problems do they have that this solves? Otherwise it’s just one mor
387.
by hhas01 7y ago
Lots of deep technical detail, but where’s the leading sales pitch? Tell us what real-world Needs and Wants drove you to create it in the first place, and how your solution fits these problems better than popular established rivals.
388.
by hhas01 7y ago
The key to being a competent software developer is really, really simple: Learn the Business . Because if you can’t/won’t/don’t understand the problem domain, how can you expect to solve problems in it?
389.
by hhas01 7y ago
Why? Because most programmers are lazy, arrogant, self-serving children . Given the choice between learning the business – requiring lots of talking to users to understand what they do and why they do it, and then writing very plain uninte
390.
by hhas01 7y ago
“Functional languages, as Dijkstra complained, tend to force wasting time by copying unnecessarily.” Citation required for your suspect AF appeal to authority/deathbed conversion story. ’Cos even dead and rotted, the corpse of EWD does

More ›