@Lensflare
No it's not,
Linux > Windows > Manure > Mac > JavaScript.

I don't mind, it's worse when people mistake my rudeness for introvertness

How is this different/better than Googles libphonenumber ?

Just get a new job, developer salaries are high enough that it really doesn't matter, enjoying your job is more important.

@dontbeevil TBH comapnies like Sony is equally overpriced and equally shit, The only thing that make crapple unique is that they have fans who claim that shit tastes good.

@Lensflare Apple has some pretty shitty charging cables. (But they're far from alone, lots of vendors include cheap cables with their products).

However, that cable looks abused.

As long as you don't tell my boss that isn't a problem.

Why not keep it simple and use a prng, they'll be equally accurate.

My work laptop has 14 cores, 64GB ram and a gpu that doesn't suck, and it's not even new or high end. Apple is overcharging for garbage as usual.

~1000x bigger than a nanoservice

Hello. I'm just a developer continually in awe of what marketers are capable of promising.

Competitive salary =
A) We'll make as low an offer as we think we can get away with once we have some hopefully desperate applicants.
B) We'll actually give you a decent salary at first but our raises won't even beat inflation so it'll be shit soon enough and we don't want our existing employees to know what we offer new people.

I'll just ask for the salary range, benefits, etc up front (before applying) and ghost them if it's too low.

Sounds like an IBK issue.

If you are familiar with .Net MVC or Django it should be trivial to pick up Laravel, the basic concepts are the same.

www.debian.org

@helloworld It will

FYI

x = [1, 2, 3]
print([y*2 for y in x])

=>

x = [1, 2, 3]
System.out.println([y*2 for y == x])

Not working all that well it seems.

Aren't you supposed to WRITE the source code for your project yourself ?

Code coverage only tells you what percentage of the code is executed during tests, not that the code is actually tested. It's useful information but enforcing X% coverage tends to result in worthless tests being written to increase coverage which makes the metric worthless.

1. Define what exactly it is you mean by phone number login.

2. Implement it.

3. Profit.

I don't understand, the official repositories contain most things the system needs and make it easy to keep it up to date and shared dependencies only have to be installed once.

Third party repositories allow vendors of proprietary software to use the same installation and update process so not only do I get system updates, I also get updates to third party applications without every single fucking application running its own update process in the background.

Good team
Good management
Good pay
Stock options
Interesting and sometimes challenging work.
Flexibile hours/location.
Recruiters being annoying cold calling spamming fucktards.

Retards who take screenshots of text instead of copy&paste shouldn't be allowed near computers.

Retards who take blurry photos of a screen with text deserve a high five, in the face, with a chair.

Good troll 10/10

I'm only dead on the inside.

As much as i love coffee this smells like spam.

PHP has a lot of good parts and ok performance these days, the only real problems is that:
1. The execution model is not suited for larger backends.
2. Unicode handling is still even worse than in c++
3. All the bad parts are still there for less experienced coworkers to fuck up your projects in subtle ways with.

Cool kids might, Adults use real tools that don't suck.

@iSwimInTheC The point of devops is to eliminate dependencies between teams, if you have a dedicated team doing "devops" all teams become dependent on it which is a retard mistake lots of companies do. Having a small team responsible for coordinating things in a large org might be good, but if your "devops" team is handling deployments, monitoring, etc for the other teams then you're doing it wrong. (If you do devops correctly you should have all competence needed to plan, design, build, test, deploy and maintain a product in the same team)

There are plenty of cases where it's acceptable. It can for example be a sensible read performance optimisation for complex models. (Hierarchical parts of the model that, rarely changes, needs to be read but is never queried can be collapsed into a single blob to eliminate expensive 1 to n joins).

In most such cases however the better option would be to use a different database.