sh87

7 ms·

1.
by sh87 4y ago
I've been a fan and user of David Seah's calendar for 3 years now. https://davidseah.com/node/compact-calendar/ I keep a pdf and screenshot version on my desktop and phone. For date ranges, I use the exc
2.
by sh87 5y ago
I very strongly agree to the idea of using the tools you already have and know to solve the problem at hand and release it. Then observe where it could use help, then seek options on specific products solving those problems and only then ca
3.
by sh87 5y ago
We needed queues. We used Redis. That fits the domain. Problem was there wasn't a good answer to "How much redis does your team need to know to put it in production". We thought we knew it well enough, we thought we knew what
4.
by sh87 5y ago
Yes I did mean RDB. Thanks for pointing out. There were many problems but at the core of it, this was us having redis write huge amounts of data to disk very frequently causing this. We could not reduce the frequency (product would not allo
5.
by sh87 5y ago
Using a tool without knowing reasonable bounds of the domain, current requirements, and how the tool (redis in this case) solves the problem isn't good advice. Case in point our team went with Redis, just the default, use it blindly wi
6.
by sh87 6y ago
I like to call it "poor engineering" and there are many forms of poor engineering I've seen. Following the analogy... painting the bottom of the bridge in same color as the terrain. Then repainting because there were color di
7.
by sh87 6y ago
counting people who have tried and failed to summit K2 vs space travel is (to me) a better quantification.
8.
by sh87 6y ago
For me this was a good starting point. https://cstack.github.io/db_tutorial/parts/part1.html
9.
by sh87 6y ago
I use multiple media. Nothing beats the fluidity, ubiquity and the sheer aesthetic quality of pen on paper. Excellent for diagrams and notes as I am discussing something on a call, or explaining things (mostly yo myself) consuming informati
10.
by sh87 6y ago
Neither did I. I was introduced to Eclipse before I got my first job and today, 9 years later it still gets the job done. I briefly use IntelliJ IDEA CE only for one static analysis plugin that works better in IDEA, most code editing is in
11.
by sh87 6y ago
Yeah but...but... that would just get the job done. Nothing to write about, nothing to whine about, no weird dependencies being pulled, nothing to hand-wave, nothing to yell and humblebrag about. No theatre. You are right, this IS madness
12.
by sh87 6y ago
> Philosophy will get through times of no money better than money will get you through times of no philosophy. Good quote! I always feel philosophy is the abode for people who couldn't get sucked in by religion.
13.
by sh87 6y ago
I suspect water resistance played a part in moving in this direction.
14.
by sh87 6y ago
If you bet big, you may lose and eat the dust. If you don't, and play cautiously, your competition will eat your market and starve you. You still eat the dust. I just don't get it.
15.
by sh87 6y ago
Also curious is the case of Pebble. Great product, priced right, small set of customers who swore by it, did one thing really really well. Now its dead.
16.
by sh87 6y ago
I suspect legal liability to be a big factor. I imagine, for a manager to get rid of someone on performance grounds needs heck a lot more work and time than getting on the company wide blanket firing bandwagon. "We hate to let you go b
17.
by sh87 6y ago
My previous comment feels snarky, did not mean it to be so. I apologize.
18.
by sh87 6y ago
Sooo... the design is not good, performance is very very poor, plugins are clunky, reporting is also poor, there's no mobile client ..... but you're happy with it. Hmmh, alright.
19.
by sh87 6y ago
> All votes shall be counted by honest and stalwart men of virtue Hah, had a good laugh out of this. Thanks for sharing.
20.
by sh87 6y ago
Had never heard of drawabox. Loved their description[0]. Resonated so deeply with me. > Drawabox's goal is to provide beginners with a strong foundation, and to equip them with the things a lot of other courses and tutorials tend to
21.
by sh87 6y ago
I'm learning to say no.
22.
by sh87 6y ago
> never again use anything proprietary or even non-human readable 100% agree with this. I have settled on a very lightly (headers and lists) formatted markdown file. I like how I can just click on bookmarked link from the rendered HTML f
23.
by sh87 6y ago
Link [1] to HN discussion around the Mazda announcement [1]: https://news.ycombinator.com/item?id=20200335
24.
by sh87 6y ago
What seemed like a straightforward product turned out to be an intricate challenge. The problem with being a small shop selling POS products is finding customers at the right time. It is very sales intensive process. You have to reach them
25.
by sh87 7y ago
I totally agree with this. I have worked in stable, long term, revenue generating projects that relied on java and its slow stable releases. I now cherish that we could focus on features and not have a "Migrate to Java x.x" story
26.
by sh87 7y ago
Any references backing these broad claims ?
27.
by sh87 7y ago
Although its a preference, I don't seem to share your concern. A half yearly summary of distilled main themes, decisions and learnings has been crucial for me to continue my journalling process. When I want to know what I was doing lat
28.
by sh87 7y ago
Some observations I'd like to share based on my experience journalling for the last 5 years. * Brevity is important. With journalling, it is very tempting to go off on a rant. Feels good at the time but its usefulness declines rapidly
29.
by sh87 7y ago
> What are the things that D3 did right to get the acclaim, and why does it keep it for so long? As a dev, what D3 did right for me is kept the code stable, provided clear sample code for most use-cases, the internet (thanks folks) made
30.
by sh87 7y ago
Just saw a similar Show HN post [1] comparing usb-c hubs [2]. Am I spotting a new trend ? [1]: https://news.ycombinator.com/item?id=22152736 [2]: https://www.usb-hubs.org/

More ›