๐๐๐ v1.0.0! @nvnh/clock is a small library without dependencies for mocking time in #javascript.
https://t.co/nkP3ylKpjS
After using it for a while in production, a few bug fixes and usability improvements, it was time to make it official.
@BoyUnfit@BStulberg I think it means making concious decisions not to do things based on self-awareness instead of trying to find "balance" doing everything.
@nintendobenzo@astrodotbuild I didn't need a CMS with Astro because it can import Markdown files. The most recent posts only have text, but there us more rich content in older posts (mostly code samples)
Just converted my website from Wordpress to @astrodotbuild and now I wish I did it sooner ๐
It's much more lightweight, much easier to host and to my surprise, it didn't take a lot of time.
https://t.co/cmh5iNa6WD
Just published a Javascript package called @nvnh/clock, a small library without dependencies for mocking time in Javascript: https://t.co/nkP3ylKpjS
It's inspired by this clock package for Go I really liked working with: https://t.co/zpiXwL71JU
If you feel like your diagram is getting too complicated, you're either trying to communicate too much in 1 diagram, or the problem is not with your diagram, but with an overcomplicated architecture.
"Our architecture diagram is getting complicated, how do we fix this? ... change your architecture." Good stuff by @simonbrown .
https://t.co/vn5GbQdyNo
Great points by @davefarley77 and @tdpauw . "Code reviews are not there to catch bugs." They're there to catch low quality code. New low quality code does not necessarily have more bugs. The real problems start when you start building on low quality code.
High growth rates (in an industry, community, startup, etc) mean you have a lot of newbies; having a lot of newbies (persistently) means you have high growth rates.
One of these intuitions which people get repeatedly surprised about, so, mentioning it out loud.
A suggestion:
If your dev team does great work, find ways to tell the rest of the biz, in ways that they will understand and appreciate.
Try and do this without talking about the technology!
That's a good point and the reason I included "Make an effort to understand legacy code" in "3 underrated things great developers do" https://t.co/qfpFPyEMdN
When something isn't obvious, people may declare it complex.
"If I don't immediately understand it, as smart as I am, it must be because it's too convoluted. That's the only possibility."
Anything unfamiliar is declared "complex."
This! I once had a discussion about the need for reactive streaming for our backend-frontend communication. If we need reactive streaming to the browser, we have a design problem. We don't need to throw on complicated tech, we need to change the design.
Sometimes, a performance problem is actually a design problem.
Example: โHow do we fix the performance of this page showing 1,000+ items?"
Answer: Stop showing so much stuff at once.
What user can absorb 1,000โs of items? Make it easy for the user to find what they need.
Kubernetes, Event Sourcing, Chaos Engineering, ...
People are attracted to sexy, complex-sounding things because it's cool to talk about them, and they can act like it will fix all of their problems.
So let's talk about underrated things developers do: https://t.co/qfpFPymCZF
@johncutlefish It was especially stressful when you were on support duty (lots of small tickets) and someone would come up and ask you a question. "What ticket is this?" would be your first reply because it was hard to "hide" the time in the support tickets.
@johncutlefish I suddenly remember an angry e-mail from a manager of the IT department that said no invoice would be paid that didn't have all time accounted for in JIRA!