
Development Tooling engineer @AdyenDevs. @MockitoJava core developer. Former @ChromeDevTools, @Polymer. Completed Master Computer Science at TU Delft
Joined January 2013
- Tweets5.8K
- Following135
- Followers1.6K
- Likes39K
Tim van der Lippe retweeted
After months of work (and years before me!), I've just sent the PR that converts TypeScript itself to modules. The compiler is 10-25% faster, the package is 43% smaller, and more. github.com/microsoft/TypeScr…
Tim van der Lippe retweeted
On Oct 25 around noon we saw a significant spike
in test failures running in our physical (phone) device labs.
Why did this happen .... Turns out even though our devices have wifi off and no sims there is still a vector of non-determinism...
Tim van der Lippe retweeted
I find this interesting because the longer my career goes, the more I prefer simple and limited (not referring to React, just generally).
Context is everything in software so hard to define hard rules but I like simple because generally it means fewer footguns.
Replying to @housecor
React 2014: Simple, but limited.
React 2022: Powerful and remarkably flexible, but intimidating and fragmented. A massive number of compelling options to consider. The hardest part is keeping up with the churn and choosing between multiple compelling options.
Tim van der Lippe retweeted
✎ LET'S TALK ABOUT WEB COMPONENTS: bradfrost.com/blog/post/lets…
Web components are part of the web. They are good for the web. We should be rooting for them.
Tim van der Lippe retweeted
Because web components are native to the web, they can travel to any web-based environment. They can be plugged into a WordPress/Drupal/Contentful/whatever site or integrated into a React/Vue/Angular/whatever app.
Of course reality is more complicated than that rosy picture.
Tim van der Lippe retweeted
A recent tweet about running 1000 tests in 1s for @preactjs got a little attention. Here's a blog post diving into all the tricks and optimizations we applied to achieved that⚡️
marvinh.dev/blog/running-100…
Running all 1002 tests for @preactjs takes ~1s.
This means new ideas can be tested instantly due to the short feedback loop. Makes it much more enjoyable to try out new ideas.
Super glad that we invested early on into a fast test setup.
Tim van der Lippe retweeted
Gather 'round, it's story time.
A number of years ago, I was hired by a company to rebuild a component library for their design system. The one they were replacing was built with AngularJS, but AngularJS was old and rickety and nobody wanted to use it anymore. 👇
Tim van der Lippe retweeted
Quick reminder!!
Code Reviews Are Not Only About Bugs! Only 15% of the comments are about defects! Code reviews are also about collaboration, knowledge sharing and mentoring.
Tim van der Lippe retweeted
The primary problem w transpiling is the errors, and especially stack traces, of sourcecode becomes useless when debugging.
Sourcemaps often do not work, leaving you blind to resolve issues.
The solution is to keep staging (code you write) as close as possible as production.
Tim van der Lippe retweeted
This is not a drill!
Improvements to the *in operator* might be coming in TS 4.9 🔥🔥🔥
github.com/microsoft/TypeScr…
Tim van der Lippe retweeted
Reminder, and slight change for tonight!
We're still hosting a #java and #testing meetup tonight. But @TimvdLippe just got sick (🫂), so instead @beppecatanese will give us a talk about @OpenApiSpec !
@mauricioaniche will speak as well 😊
meetup.com/eu-adyen-develope…
Tim van der Lippe retweeted
"Don't assume anything" is the golden rule I live by.
There is a tendency in our industry to solve problems by piling more code on top of it. But the zen of coding lies in changing the system so that these problems can't exist in the first place.
Tim van der Lippe retweeted
Do you have a web app running on a legacy framework or library? Are your devs experiencing fatigue and churn by updating the ugly code and a rewrite is just too much work to consider?
This is where @buildWithLit comes in. With WC interop you can update only what you need!
Tim van der Lippe retweeted
🔥 New Post: Announcing InAppBrowser - see what JavaScript commands get injected through an in-app browser
👀 TikTok, when opening any website in their app, injects tracking code that can monitor all keystrokes, including passwords, and all taps.
krausefx.com/blog/announcing…
Tim van der Lippe retweeted
💥 New Post: Instagram & Facebook tracks everything you do on any website in their in-app browser
krausefx.com/blog/ios-privac…
Tim van der Lippe retweeted
Fresh from a recent study: a single visit to a website generates an average of ~1 gram of #CO2 with some websites generating up to 76 grams.
More details in our recent blog post: s2group.cs.vu.nl/2022-08-04-…
Data: github.com/S2-group/co2-and-…
Work by Ivan Ivanov (@VUamsterdam)
1/2
Tim van der Lippe retweeted
Classes got done dirty. The exegesis of React Hooks relied too much on claiming certain problems were intrinsic to classes, when they were more like deficiencies in the design of React’s class-based API, IMO. – at Manhattan, NY























