Dan Bender

This looks nice:

It will never be perfect – the idea of the web is to release code into the unknown. All you can do is make sure you don’t deliberately make it harder for people by expecting a certain technology or hardware to be available.

You can always find a problem that is not possible with standard techniques – you can then use JavaScript and the DOM to solve that problem. Then you have the problem of people using your JavaScript solution and be ready to fix it for all the new platforms, browsers, environments and connection speeds to come. That’s what web development is about. That’s what browsers need to do.

“Technique $X is the best to use” is a fleeting statement – table layouts were the only way to create a multi column layout and got replaced by CSS. CSS layout with positioning and floats is a make-do solution, too. Flexbox is the up and coming solution to the problem of layout on the web. It is not ready across all browsers and not backwards compatible if you want all browsers to create the same layout. See where this is going?

There is no “one” solution for any web development problem – this is the beauty of the web. It is the “bring your own solution” platform. If you want to make it better for everybody, use standards and let the browsers worry about the performance issues and do report them to the browser makers. Everything else is patchwork and will be debunked as “not working as expected” over time

In 90% of the cases mythbusting articles solve one problem – the argument is not that a technology is flawed, the argument is that it is not good enough to solve problem $x. Which is OK, there will always be things that can not be done. The real question is “do you need to solve problem $x and what dependencies, issues and problems does the solution bring along with it”?

Everything on the web is best achieved with a mixture of technologies – CSS animations are great for certain jobs, but will not be good enough for others. You can achieve almost everything with JavaScript but that doesn’t mean you have to or should. Flash was used for a lot of things, some it was damn good for, others awful. There is no way – ever – that one technology can 100% replace another. Our use cases change and we should strive to use the technologies that gives us the best result for the least effort whilst allowing browsers to optimise for us. It is not about what we can do, it is about what makes sense to do.

This (..) is the recommended solution from the Google help pages.

Hi,

the app is called Lift @ https://lift.do/

It's fairly simple; it allows to define goals and track them by simply checking them off. Their hypothesis is that regular tracking helps build habits. I agree and I have been using it ever since it came out.

Cheers

I have been coding for 100 days in a row.

There were days when I coded from early AM until, well, early AM and other days when I just coded for a little bit – but I kept that streak going and am going to keep it up as long as I can.

It is hard to believe what I have learned in those 100 days.

Only 100 days ago, I barely knew what a Terminal was, and now I even prefer to use iTerm in my everyday life when e.g. moving files on my machine. I went from not knowing anything to still not knowing anything but nevertheless writing full-stack web applications and following best practices like TDD.

Biggest learning?

Probably: 

I love doing this stuff.

Learning is awesome and I am (most of the time) insanely grateful for all there is to discover.

All we do is mess with data. We send data, we store data and we receive data. We perform operations on data. Ergo: programming is not magical. It is the single most creative and challenging craft I have ever engaged in but it is not magical.

Now that I'm back in GER (cold!), I feel like there is one more thing to say:

Thank you. For everything but especially for the support and the amazing friendships we built. And this new superpower – damn, I'm hooked.

Lots of this* for y'all.