|
|
Cool stuff.
Somehow reminded me of Air, specifically Sonic Armada[^].
|
|
|
|
|
|
I like the Pickle Rick and Not Quite My Tempo (great movie!) ones too!
|
|
|
|
|
Here's the endpoint:
someapi.com/image/someImageID?xy=1
Think about it.
(Besides the WTF experience of using a flag parameter to indicate the endpoint is returning the dimensions rather than the image)
modified 21-Nov-19 15:59pm.
|
|
|
|
|
I tried to browse to that endpoint and expected to see something
someapi.com is not for sale yet
Given that endpoint, I'd expect some image on a single pixel.
The back-end could transform the image to a 1x1 image and save some bandwidth.
I'd also expect x and y as separate parameters for rectangles.
For example: someapi.com/image/someImageID?x=100&y=150
Probably because I was thinking of Placeholder.com[^]
That endpoint looks pretty much the same: https://via.placeholder.com/150[^] (which returns a 150x150 image/grey block)
Or: https://via.placeholder.com/468x60?text=Pretty+cool[^]
I use it for mockups.
|
|
|
|
|
/ravi
|
|
|
|
|
I thought about it, but I don't get your point (haha "point").
What is wrong with the format?
Personally I would probably use different methods, for example:
someapi.com/image/someImageID
someapi.com/imageinfo/someImageID
Purely on the basis that the return types are going to be different. But it's not like it really matters... does it?
|
|
|
|
|
I think Marc is talking about the WebAPI conforming to better naming conventions that follow like the example of ASP.NET MVC routing:
routeTemplate: "api/{controller}/{action}/{id}"
And he is saying that because it would be far more intuitive to discover how to get the dimensions of the image.
someapi.com/api/Images/Get/15
someapi.com/api/Images/GetDimensions/15
modified 22-Nov-19 11:21am.
|
|
|
|
|
raddevus wrote: I think Marc is talking about the WebAPI conforming to better naming conventions that follow like the example of ASP.NET MVC routing:
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
I refuse to post a link to JIRA, but not everyone may have heard about https://monday.com/[^]
Anyone use it? Personally, my view is, a wall with post-its would be better than JIRA, so I'm looking forward to the company making a change to something, anything, that isn't JIRA.
Yes, I'm opinionated about JIRA.
|
|
|
|
|
I looked into monday.com but found it did not have a few features I needed. I wish I could remember what those features were now.
So no, I never did use it beyond the 7 day free trial.
Still haven't found a different option but we're small enough that spreadsheets are still working fine.
Social Media - A platform that makes it easier for the crazies to find each other.
Everyone is born right handed. Only the strongest overcome it.
Fight for left-handed rights and hand equality.
|
|
|
|
|
JIRA, a good idea, just done wrong
|
|
|
|
|
Management has decided we should switch to JIRA, looking forward to using it ...
|
|
|
|
|
|
Marc Clifton wrote: Personally, my view is, a wall with post-its would be better than JIRA
That's essentially what Trello is.
|
|
|
|
|
So Monday doesn't work on Mondays because it has bad case of Mondays ?
I'd rather be phishing!
|
|
|
|
|
+1 for post-it notes. I have found it to be a very effective workflow to write my assigned Jira tickets onto post-it notes, work off the post-its, and then reconcile my work back into Jira the day before the PM does reporting.
As for Monday, I haven't tried it, but I don't like them because I keep seeing ads for it almost every day.
|
|
|
|
|
I added your suggestion as a JIRA ticket to be reviewed by whoever might be concerned!
|
|
|
|
|
We have been using VSTS and it works pretty well, linked with TFS and all that. I prefer it over GIT and/or Jira.
|
|
|
|
|
VSTS is OK, but in preferring TFS over Git makes you quite a rare find.
"'Do what thou wilt...' is to bid Stars to shine, Vines to bear grapes, Water to seek its level; man is the only being in Nature that has striven to set himself at odds with himself."
—Aleister Crowley
|
|
|
|
|
Definitely 1 up for VSTS. The work flow and add-ons really help
|
|
|
|
|
I also prefer vsts:tfs over git. It was simpler and more forgiving. Git has too many commands to remember. Also tfs integrates well in visual studio.
|
|
|
|
|
Have not used Monday - but also found Jira to be slow and clunky. Asana is another option that is quite usable. Teams has some limited capability with a good UI. My recommendation would have to be silolog.com which is simple and effective.
|
|
|
|
|
My company is moving from IMS and VersionOne to JIRA, I've not had the chance to try it out yet but other teams seems to think it's an improvement.
You don't have to be mad to live here [UK], but it helps.
|
|
|
|