<:think_woke:378717098681171988>

stronger cpu?

You root your phone?

am I blind

yeah, the 660 is better than the 636

yee I'm blind

@Deleted User
the one i'm using? no

it's old as fuck

no root phone-chan

You can loose warranty, you must be careful with this.

@Deleted User
Yeah, do it when the warranty is done

@Fulcrum010 it's not hard to trigger @Reaps

@Fulcrum010 for 30 euros a month and 100 up front for 2 years I get a 6gb contract with a galaxy s8 I get to keep afterwards

seems good

https://www.youtube.com/watch?v=WnzlbyTZsQY

Overall, it's telling how MS treats their most essential engineers, why their software sucks at so many levels.

>I'm a unicorn
🤣

```
Griffin Aasen
2 weeks ago
Once they found out they were both robots they were talking about God, and seeking bodies. I'm moving to the next galaxy```

I feel like the same could be said for the code in most programs nowadays

@Reaps @Deleted User @Jab https://twitter.com/thekitze/status/999549624598884353

Nice

@meratrix

:/

This is my life right now.

because coding is easy!

Spent it on the dinosaurs and not the pizza eating nerfherder

?

What if it went like this:
- I need a team of coders. Since it needs to be fail-safe code, with human lives at stake, it needs to be carefully designed, thoroughly tested, and ...
- I have faith in you, you can do it by yourself.
- (Fucking old geezer... I could burn the whole place down, you know?)

What’s the worse coding habits you guys have seen:

```using namespace std;```

I'd say, that's fine when done in a single .cpp file. But last week or so I've heard some idiots ("game devs") still use "Unity Builds".

For those that don't know, it's when you have a `everything.cpp` file with
```cpp
#include "main.cpp"
#include "utils.cpp"
#include "player.cpp"
#include "thatotherthing.cpp"
#include "networkfunctions.cpp"
#include "someotherrandomcrap.cpp"
...
```

Never mind that changing one single file now requires rebuilding your entire program, never mind that now you can't do parallel compilation in your shiny, expensive build machine with 32 cores, never mind that a .cpp file might just define a macro and never undefine it, never mind that multiple files might have a `static int profiler_counter;` variable that are now violating the one-definition-rule and are now shared across everything...

At least now you don't have to learn how to have more than one file on your IDE, so that's a win, right?

What's that, you ran out of memory for the compilation? Then delete some code!

Worst coding habit I've encountered is when the programmer knows absolutely nothing about other people's code. He never read code from anybody else for 10 years or more, has no idea about terminology and concepts. So he writes shit like
```cpp
void context_activate_get_task_prepare(Worker* worker,
int number,
char* buffer,
Context **ctx,
int* explanation,
int level,
int sublevel,
float delay,
ContextExtra *activity,
stack<int> connection,
char file,
char* file2,
int avoid)
{
// ... you don't want to see what's in here
}
```

And no, the documentation for this function doesn't make any more sense than the argument names.