wheresvic4

12 ms·

91.
A Byzantine failure in the real world(blog.cloudflare.com)
1 points by wheresvic4 6y ago|0 comments
92.
An Introduction to Lock-Free Programming (2012)(preshing.com)
149 points by wheresvic4 6y ago|36 comments
93.
Sorry React, but I can’t keep up anymore(medium.com)
2 points by wheresvic4 6y ago|1 comments
94.
What Makes a Great Product Manager(knowledgeartist.org)
1 points by wheresvic4 6y ago|0 comments
95.
The Reality of a 10x Engineer(medium.com)
3 points by wheresvic4 6y ago|0 comments
96.
Twitter's Fleeting Product Roadmap(themargins.substack.com)
2 points by wheresvic4 6y ago|0 comments
97.
Chinese Chicken Fingers and the American Dream(themargins.substack.com)
1 points by wheresvic4 6y ago|0 comments
98.
Building a voice assistant to control music(smalldata.tech)
1 points by wheresvic4 6y ago|0 comments
99.
Levels of annoying the users of your API(ozlabs.org)
3 points by wheresvic4 6y ago|0 comments
100.
Greg Kroah-Hartman: Lessons for Developers from 20 Years of Linux Kernel Work(thenewstack.io)
2 points by wheresvic4 6y ago|0 comments
101.
by wheresvic4 6y ago
It's funny, I also ended up building a custom static site generator and it was actually really simple to do so! When I initially started googling around for custom static site generators, I could not find much content so I just wrote a
102.
A static site generator in 100 lines of code(smalldata.tech)
2 points by wheresvic4 6y ago|0 comments
103.
by wheresvic4 6y ago
Hmm, seems like I am somewhere in the middle - my blog is run on a custom static site generator and I have around 50 blog posts, which are mostly technical how-to content, including of course one on writing your own static site generator :)
104.
Building a secure Node.js development environment via containers(smalldata.tech)
1 points by wheresvic4 6y ago|0 comments
105.
Building a secure Node.js development environment via containers(smalldata.tech)
2 points by wheresvic4 6y ago|0 comments
106.
American Airlines is bringing back the 737 Max. Here's why that's disturbing(zdnet.com)
4 points by wheresvic4 6y ago|0 comments
107.
Technology for Humans(themargins.substack.com)
2 points by wheresvic4 6y ago|0 comments
108.
Anemic Domain Model(martinfowler.com)
1 points by wheresvic4 6y ago|0 comments
109.
Macro Trends in the Tech Industry(thoughtworks.com)
2 points by wheresvic4 6y ago|0 comments
110.
by wheresvic4 6y ago
Hear hear - they get my vote for citizenship as well.
111.
How Facebook is bringing QUIC to billions(engineering.fb.com)
2 points by wheresvic4 6y ago|0 comments
112.
Forcing Functions in Software Development(coderefinery.nz)
2 points by wheresvic4 6y ago|0 comments
113.
by wheresvic4 6y ago
Thanks for the appreciation - I essentially wrote it for myself because I had the same issue every time I had to deal with a Dockerfile :)
114.
Docker in 10 Minutes(smalldata.tech)
38 points by wheresvic4 6y ago|6 comments
115.
Copying Objects in JavaScript(smalldata.tech)
2 points by wheresvic4 6y ago|0 comments
116.
Copying Objects in JavaScript(smalldata.tech)
3 points by wheresvic4 6y ago|0 comments
117.
by wheresvic4 6y ago
I really enjoyed your setup to the question and it did really make me think about issue management in deeper detail. I think that one of the points that you raise is quite valid - that issue tracking should really be integrated into version
118.
A static site generator in 100 lines of code(smalldata.tech)
1 points by wheresvic4 6y ago|0 comments
119.
A static site generator in 100 lines of code(smalldata.tech)
1 points by wheresvic4 6y ago|0 comments
120.
What to expect in a code quality assessment(smalldata.tech)
1 points by wheresvic4 6y ago|0 comments

More ›