melissalobos

25 ms·

241.
A large-scale study on research code quality and execution(arxiv.org)
2 points by melissalobos 5y ago|1 comments
242.
by melissalobos 5y ago
I would just explain the situation and apply: "Hey {NAME}, I saw you had a new job posting I think I would be a good fit for. We met a few years back, and I forgot to write back to you, sorry(I had some issues at that time that took a
243.
by melissalobos 5y ago
I liked this part: > To use an analogy, if SICP were about automobiles, it would be for the person who wants to know how cars work, how they are built, and how one might design fuel-efficient, safe, reliable vehicles for the 21st century
244.
by melissalobos 5y ago
> So, how onerous is package management in Slackware if there is no dependency checking? I can't say that I have used Slackware ever, so I don't know. But I have used a Linux distro where every package was statically linked by
245.
Comparison of free and open-source software licences(en.wikipedia.org)
1 points by melissalobos 5y ago|0 comments
246.
by melissalobos 5y ago
In the end Electron may be slow and bloated, but it is easy to distribute and you can make it look exactly how you want. People often say they want apps to look "native", but really most people I have met don't really care t
247.
by melissalobos 5y ago
This seems like it is the second time we have had to learn about the importance of maintain large open source infrastructure projects like this. log4j and openSSL before it, show that these projects aren't just the responsibility of t
248.
Notes on Hiring Developers(izente.com)
1 points by melissalobos 5y ago|0 comments