Two words... Continuous integration

@devgianlu queue Dr Evil quotation marks....

"Temporary"

Unit testing / clean code

What @pk76 and @Root said. Plus there's always the possibility to help people that are less fortunate through your development (e.g. https://www.bemyeyes.com/)

Although the term is definitely overused, technology has so much potential to change people's lives. It just depends on how you try to accomplish that (i.e. what jobs are you willing to take).

If you read gc as garbage collector this makes much more sense

Well at least they're ranting about something 😅

Well...tell us about it 😄 what language? What branch of maths?

And thus V8 was born

Dat cyclomatic complexity

10X Developer stuff...

@devTea unfortunately can not upvote more.

Nobody cares about your preference. Just make it consistent..

Absolutely fantastic fucking Idea. But what if there are two competing importants from the same day 😱

How about the number of exclamation marks to signify the importance additionally.

Or how about making it comparative:
1. !important
2. !importanter
3. !importanterer
4. You get the gist

Don't be sad. Rage, rage against this fucking awful bullshit.

Never accept.

Domain Specific Language? I doubt it in this context...

@jak645 agreed. The only thing I understand differently is POST. I think I've read somewhere that it's kind of a default Verb. Not meaning anything particular. You can use it for anything the other verbs don't already do.

+ The ID part of your rule is a little misleading. It's all relative to the URI.

@h4xx3r patch is for partial updates, correct. Put is for overriding an entire resource.

Your API is not an interface to the Database. Your API is an interface to the Business Logic. Soooo depends on your Business Logic :D

But as a general Rule of Thumb:
Different Resources = Different URLs
Different Operations (update,create) = Different HTTP Verb (PUT, POST)

@M1sf3t Hope there is a whisky bottle on the bottom of that brown paper bag

Translation: " I neither have the technical knowledge nor is it my job to know about the problem in detail. Please fix what is fixable and analyze what can be done to make the rest fixable and come back to me with solutions."

While I hate bad PMs, I really thank all the good ones I've had.

@inaba To be fair, the IdentityProviders that are prebuilt are what you call magic. You can always implement your own one (like I did) that does exactly what you want.

You could pad the box contents or even make them centered vertically and horizontally.

I think you are on the right track with 'letting them breathe' but right now the content is just stuck to a side of the box.

I have to use the web interface because corporate....

No way to deploy locally?

I agree. It's not going anywhere, but maybe for select use cases it will.

I mean we already only use class state for handling DI in our enterprise applications so as to minimize side effects and not complicate our unit tests.

@Conrad I definitely get it. Android is most certainly not made for only enthusiasts any more :/

I kind of long for the time when it was only geeks who would want to customize every single thing on their device that had an Android.

But then again I'm at a stage in my life where I just don't bother anymore...

@Conrad I'm guessing battery life

Definitely not const for me ;D

@mishaor Done :D thanks

I'm just glad you didn't sudo...

As for the idea of having the specs in something so chaotic like sharepoint: just... don't

I like to have the specs only in one place for a user story or feature. Not on 3 different sharepoint sites in different versions where maybe not even all Devs are authorized.