1,682 karma · joined February 19, 2010
You're right, there are other solutions out there. Glean's the pricey one aimed at big companies, but from what I've seen, the others are either still in development or not quite hitting the mark. My research shows this is a problem for smaller outfits too, and I think there's room for a solution that really works.
On your points:
1. Latest view on a topic: Yep, this is a big issue. I'm looking into ways to integrate metadata to help with this.
2. Knowledge in people's heads: Good point. Actually, I'm hoping my tool could encourage more knowledge sharing. The idea is that if it's not written down, the AI can't retrieve it, which might motivate people to document more. Still brainstorming on how to make this process smooth and not feel like extra work.
3. Information silos: Definitely a thing. My approach is to mirror existing access restrictions - the tool can only access what the user can. But I'm thinking about how it could still help improve cross-team communication within these limits.
Your idea about niching down is interesting. I'm casting a wide net right now, but focusing on specific roles could help tackle unique challenges more effectively.
I'm curious - what's your experience with knowledge management systems? What's worked well for you, and where do you see the biggest gaps?
Really appreciate your insights. This kind of feedback is gold at this stage.
Bazel recognizes it's compiling on macOS, so it's using clang-compatible flags, which are incompatible with gcc. You should use the default host compiler, as stated in the [configure output][1] in the post. /usr/bin/gcc is for all intents and purposes clang on macOS.
gcc-7 is only installed to provide libgomp which is otherwise missing from a standard macOS installation.
I'll update the post to make it clearer. Thanks for pointing that out!
[1]: https://gist.github.com/crmne/a22858264d68dd9fe935fc4ee48e04...
This story was also posted in the comments.
+ Rubinius will remove the GIL ("the work has already begun" -- Yehuda Katz http://yehudakatz.com/2010/08/14/threads-in-ruby-enough-alre...)
+ MacRuby will be even faster, more stable and more documented
It will be an awesome end of 2010/2011 for Ruby programmers.
An application's phone interface has to be different than the desktop one, and since there is no programmatic way to adapt the desktop interface to the phone, it has to be rethought and then reimplemented.