To all complaining about light themes being too bright: have you ever tried lowering the brightness of your screen? I find that a much more effective solution especially when switching work places (coffee shop vs. man cave vs. park).

@Sourcerer Why isn't it relevant? And how is the age of basic research detrimental to its value/truthfulness?

Teach a course or two on programming to beginners and you'll realise you know a shit load of stuff.

I hate that. The whole online dev community is going "document your work!!1" so you do. In come the leet haxors who go "I don't want an API, I want the whole data yada yada" or "I didn't read the docs, I inspected the calls to this other rando, closed and unsupported API". GRMBL.

Vacation: code without deadlines breathing down your neck and passive-aggressive clients trying to be nice.

Why are you having a hard time? Has your knowledge become obsolete? Is it broad but shallow? I'm a full stack dev as well and am wondering (stressing to be precise) about these questions.

They switch to German to show they're really serious about this.

*hides from the stereotype police*

To learn stuff you didn't know you didn't know?

I'd say we need more not less ethics and morals. Some nerds should stop doing stuff simply because it's "cool" or possible.

This is getting old. Charging it for the day takes two minutes (as owners point out each. and. every. time) . Plug it in, fetch a coffee, unplug it and enjoy a nice mouse that doubles as a small touch pad*.

I wish folks who don't own it would stop ranting about it.

*Fire up Figma.com and enjoy butter smooth panning and zooming without releasing the mouse.

@Bitwise Crab, that's a typo!

Has Apple announced the new MacBook?

try:
# to fetch a remote resource which may fail in a gazillion ways
except:
# something went wrong, try again later

is why.

@geaz How is working faster during working hours the same as working during a holiday?

👌🏼rant.

So you're staying home on Mon and Tue? Good!

Send a PR and teach those 10x developers how to write code for us normies.

Very relatable.

I also suffer from the self-induced stress of keeping up with everything. For example, I've meant for a while now to get proficient with JavaScript promises but haven't gotten around to diving into them due to lack of time and a suitable project. Last week finally brought a new project which I decided to do in Angular. Turns out that promises are yesterday's tech, the new thing is observables. Cool, I thought, now I can skip promises. Win!

Moral of the story (for me at least): there will always be newer tech. Missed the latest fad? Simply wait for the one after it.

Also, the longer a tech is around the easier it gets to work with it because of an ever growing ecosystem (or lack therefor in which case you can skip it again) .

Figma is neat.

.

.

Very relatable. So much so that I sometimes wonder whether it's more effective to immediately start writing the bug report since it makes you look harder for the cause.

Mostly because it's the default and I want to get shit done instead of mixing and matching themes.

Why mix and match? Because not everything I use supports a dark theme thereby melting my brain every time I switch to it from a dark theme.

Also, I like to code in bright spaces preferably with lots of windows.

I prefer to regulate the screen intensity by dimming it as it gives me much more control. That's useful when working in different environments i.e. home vs. coffee shop.

I also use f.lux.

Is there a non-hacky mechanism for communicating between the different instances?

Been there, hated that. Foundation for Emails saved me.

🇧🇬🇳🇱🇸🇪🇳🇱

(in that order)

Tip from a fellow Angular noobie: read http://reactivex.io/rxjs/manual/... instead of Angular's discussion about Observables.

The ReactiveX docs are much easier to follow and understand. I don't understand why the Angular team decided it is a good idea to describe how to create a custom multicast Observable when there's Subject...

I'm learning Angular as well!

Skip the configuration part by doing everything through angular-cli.

What I'd like to complain about is the docs (again!). Just like AngularJS they are... pretty difficult to parse.

Take the tutorial for example: it covers a lot of ground but because it's written as a story it's super difficult to parse quickly. Important stuff like Subjects is buried deep in one of the chapters and is not covered at all in any other parts of the documentation.

Luckily it's a popular framework so Googling results in useful explanations and blog posts.

Good luck!

Stay away from self-driving cars, ok?

I read that as "visual threat" and went: "yes, yes it is. Oh, wait... ".