mehagar

7 ms·

31.
by mehagar 1y ago
How could you possibly plan out "everything" in advance? Code itself would be the only way to explicitly specify the "everything".
32.
by mehagar 1y ago
Yes, the original set of web technologies was simply not designed with the kinds of interactive UIs people expect today. Perhaps in the future UIs can be rendered with WASM, with the common rendering libraries being distributed as a separat
33.
by mehagar 1y ago
More likely they don't even need to use useMemo if it's not an expensive calculation. They can just calculate the dependent values during rendering, which is explained in the docs: https://react.dev/learn/you-
34.
by mehagar 2y ago
More broadly it includes moving activities that are normally performed at a later stage so that they are earlier in the process. The idea is that defects found later in the process are more costly.
35.
by mehagar 2y ago
Unit tests should be independent of the environment they are run in, and pass or fail consistently. Otherwise, it is not a unit test.
36.
by mehagar 2y ago
Unit testing proves correctness in regard to the test written (not necessarily the correctness of the application itself). They're similar in that they are both typically fast to run, and that they check an aspect of the program for co
37.
by mehagar 2y ago
I like the testing pyramid specifically because it captures the tradeoffs between the different kinds of tests. Mocks can come in handy, but like anything else can be abused. We need a "Mock this, not that" kind of guide.
38.
by mehagar 2y ago
On that topic, static type checking can effectively be seen as a "unit test" that tests as well as documents the expected types for an interface.
39.
by mehagar 2y ago
That reminds me that Stripe actually maintains (or used to) their own mock for their Ruby package. This puts the burden on maintaining the mock on the library owner, where it is more likely that they would implement the mock correctly, edge
40.
by mehagar 2y ago
I agree that if you need to write mocks, it's likely that your interfaces are poorly defined. This is one of the claimed benefits of test driven development - writing the tests first forces you to design the code in a way that cleanly
41.
by mehagar 2y ago
The catch-22 with refactoring to be able to write unit tests is that refactoring introduces risk as you are changing code, and you need tests to help reduce that risk. But you can't easily write tests without refactoring. This has been
42.
by mehagar 2y ago
Clean Architecture and Fundamentals of Software Architecture: An Engineering Approach.
43.
by mehagar 3y ago
WebSocketStream is about to ship in Chrome, which adds backpressure: https://chromestatus.com/feature/5189728691290112
44.
by mehagar 3y ago
See also Web Neural Network API: https://www.w3.org/TR/webnn/
45.
by mehagar 3y ago
An additional benefit of WebTransport over WebRTC DataChannels is that the WebTransport API is supported in Web Workers, meaning you can send and receive data off the main thread for better performance.
46.
by mehagar 3y ago
It's being worked on now: https://github.com/WebKit/WebKit/pull/17320
47.
by mehagar 3y ago
Does your current company have any lower level positions open? It may be easier to switch internally.
48.
Toyota Virtual Plant Tour(global.toyota)
1 points by mehagar 3y ago|1 comments
49.
by mehagar 3y ago
The keyword is self-service. Instead of engineers filing tickets that say "please deploy my application", you have a dedicated team create an internal web app or something that lets engineers deploy their application themselves, b
50.
by mehagar 3y ago
Rather than developers not wanting to do ops, I took the article to mean that - ops is sufficiently complex - The incentive to deliver features means that ops corners tend to be cut So the suggestion is to build a self service platform that
51.
by mehagar 3y ago
https://www.hyrumslaw.com/
52.
by mehagar 4y ago
Check out https://chrome.google.com/webstore/detail/xoom-redirector/oc...
53.
by mehagar 4y ago
They're implementing that as part of their calendar service: https://youtu.be/Dw1HiYxl7CE?t=7920
54.
Zoom would like to remind you that it’s a many-trick pony(fastcompany.com)
2 points by mehagar 4y ago|0 comments
55.
by mehagar 4y ago
I think TDD is great in the ideal, but in reality I have only worked on legacy systems where TDD was not practiced from the start. Such systems are hard to fit TDD style tests into because modifying existing code often requires large refact
56.
by mehagar 4y ago
You make a good point about not being able to enforce that TDD is actually followed. The best we could do is check that unit tests exist at all. In theory, if TDD really reduces the number of bugs and speeds up development you would see if
57.
by mehagar 4y ago
"Right" implies there is some objective authority who could tell you whether you are using your time the correct way or not. Thinking about spending time this way leads me to feel guilty (I'm not spending it the right way!).
58.
Zoom PWA(pwa.zoom.us)
2 points by mehagar 4y ago|0 comments
59.
by mehagar 4y ago
Check out https://github.com/arkadiyt/zoom-redirector . You can also join meetings from https://pwa.zoom.us/wc/ .
60.
Social Skills Notes(docs.google.com)
3 points by mehagar 6y ago|0 comments

More ›