cdent
Joined 15 years ago
Karma
154
Submissions
55
Member since
Aug 24
http://anticdent.org/
View on Hacker NewsRecent submissions
Comment · 1 year ago
From what I've seen, the people who complain about go's design are people who are more concerned about the ways in which it is not correct (by some definition) and less concerned about just getting stuff done.
I don't "like" go (or any other programming language), but I'm able to get more done in it in a shorter amount of time than any other language, the created thing consumes tiny amounts of resources, and most importantly when I _or anyone else_ goes back to change something weeks, months, years later it's easy to re-establish or gain contextual understanding.
Comment · 2 years ago
One might argue that if "Spring is such a complex framework" you never should have been using it in the first place?
Comment · 5 years ago
I'm always confused by these sorts of posts because they happen often so there is clearly a problem but for some reason I've never had much of an issue. I've been using and developing with Python for about 15 years. In that time I've worked on Python projects large (OpenStack) and small (gabbi) and taken over maintenance for some old standbys (wsgi-intercept, paste to name two). Dealt with the 2->3 transition. Released a whole bunch of things to PyPI and relied on far more things that I've pip installed from there. It's been fine.
I don't know what I'm doing differently.
Comment · 5 years ago
If an entity makes profit off the back of my labour without compensation a reasonable case could be made that harm has been done to me.
Or at least a labourer may legitimately claim they wish to share "freely" only to some. And they can also choose to change their mind on any subsequent work.
This is especially the case when the entities involved are corporate, not individual humans.
Comment · 5 years ago
Disclaimer: I'm the author of gabbi.
It's great to see more and more API testing tools that use a format intending to be readable.
I personally think YAML is a bit more readable for humans so that's what I used when I created gabbi. Here's a similar test to one of the examples from apitest:
tests:
- name: httpbin post
POST: https://httpbin.org/post
verbose: true
request_headers:
content-type: application/json
data:
foo1: bar1
foo2: Bar2
response_headers:
content-type: application/json
response_json_paths:
$.json.foo1: bar1
$.json.foo2: Bar2
$.headers.Host: httpbin.org
Comment · 5 years ago
Wow, I completely disagree. What I've read of hers the writing has been great. Tight. No waste. But still very evocative.
Comment · 6 years ago
Agree. I wasn't at all convinced by the examples showing the Echo was somehow better than using the "built in" signatures, especially since there's quite a bit of handling that Echo (and things like it) makes implicit that you'll probably want to be explicit in some edge case.
Coming from WSGI, I found go's middlwares familiar and positively pleasant.
I too ended up on Chi as the router that worked well without getting in the way.
Comment · 6 years ago
Consider https://zuul-ci.org/ , perhaps?
Comment · 6 years ago
Yeah, have to wonder how this wasn't already completely obvious.
I mean, sure, it's great that it's got an official science stamp on it, but really big duh here.
Comment · 6 years ago
Anybody else get bummed out that many times that we create a lightweight thing to compensate for something overcooked (like XML) the new thing eventually ends up overcooked in much the same way?
Comment · 6 years ago
Sure, can't dispute what you say. There has to be some amount of "you must be this high to ride this ride" but you don't need to measure 7 times or whatever before thinking the first measure was accurate.
I've been on both sides of the interviewing tables many times and the processes that worked the best were the ones that involved telling stories to another another and seeing how the other reacted. You know, actually interviewing, humans having a conversation.
Comment · 6 years ago
These sorts of interviews do not find good software developers, they simply remove a certain kind of bad (not really) software developers along with a whole host of very good software developers that don't fit a very specific mold (perhaps people who write cheery blog posts about how fun it was? ...weird). Which is fine if you're the company doing the interviewing, but completely time wasting for the interviewee. In aggregate it sounds like abuse and disrespect. It's dismissive of experience, accomplishment and aptitude in favor of training to the test.
People say that Google has changed their tune somewhat over the years, but their creed has had impact throughout the industry. It's a shame.
Comment · 6 years ago
Good. I recently told my local honda dealer I wouldn't be buying another of any car because of touchscreens exactly because of the need to look and lack of tactile interaction.
Clearly this change is because of me, specifically, only me. ;)