276 karma · joined May 24, 2010
> To produce the protein needed for insulin, we need to grow microorganisms with a bioreactor and purify the protein from the culture with a protein purification system (FPLC). Proprietary examples of this equipment come at a very high initial cost and with high ongoing costs of support from the manufacturers. Our goal is to develop easy to manage, easy to repair, and affordable equipment to sustain local and community-built insulin production. > Our FPLC design is in the early stages, and we are steadily developing mechanical and electrical designs to detect UV-C absorbance and manage the concentration of two buffers via peristaltic pumps and a mixing chamber. We plan to use Arduino microcontrollers as well as the Raspberry Pi, and the finished device will make use of the open-source Ender 3 3D Printer to facilitate automated fraction collection with G-CODE input. The bioreactor design makes use of quite a few commercial off-the-shelf parts and is ready for prototyping.
If we keep the majority of the code pure and straightforward, we can deal with state and I/O with other constructs, like atoms and records, only where we need to (doing this systematically tends to lead me to some variation of the functional-core/imperative-shell pattern). STM, multimethods, macros and whatnot are cool and have their uses, but after a while I think the really cool thing is how little do we need to resort to fancy stuff and how much is accomplished with just functions and data.
This one tells the story from the precursors to time-sharing to PARC, using the figure of J.C.R. Licklider as a pivot, and was recommended by Alan Kay as better than Dealers of Lightning. I personally enjoyed both.
A few questions come to mind now: 1 - This new demo, with the messaging app sample, and references to "my pm wants this or that" seems to point a change in positioning, from targeting non-programmers to professional programmers. Is this accurate?
2 - Is there a plan to integrate the grid-style or the adlibs style UI into this new iteration?
3 - If non-programmers are still a target, it seems to me that the ease of importing data from external sources would important to reach broad usage. Any research here?
4 - Html and css might be a hurdles for new users, any way Eve will help on this front?
(edited for formatting)
About the other point, regarding the future of the country, I did not mean the impeachment going through would undermine our democracy - this sort of discussion has no place here. Just that the overall economical and political landscape is cloudy at best. Operation java-jato is likely a good thing, but a "Mani Pulite"-like outcome, with corrupt politicians passing essentially pro-corruption laws, and the ascension of an inept "strongman" (in italy it was Berlusconi) is something that can easily happen in the coming years.
In particular, it is clear the congress voted for her ousting due to a series of reasons unrelated to the allegations. One reason is the dismal state of the economy, likely due in no small part to Roussef's policy decisions. Another reason is that a majority of politicians, from all major parties, are facing serious corruption charges from a large, unprecedented, investigation conducted by the federal police, and the impeachment acts as a diversionaty tactic (there are recordings proving this is not a conspiracy theory). Lastly, there is the usual power struggle, that is fiercer and more complex in an environment with many political parties.
In all, a complex scenario that does not bode well for the immediate future of the Brazilllian democracy.
In particular one side-effect of being a beginner is that one spends a lot of mental energy on the technique, leaving less room to focus on other important aspects. That gets better with time.
http://www.leafpetersen.com/leaf/publications/dtp2013/lambda...
Excited because I found myself agreeing with every point: isn't it obvious to everyone that the programming experience could be so much better? We created wonderful tools for graphical expression and number crunching, that keep getting better [1] [2], while our own day-to-day tools remain basically in a rut.
Disappointed because it seems LightTable is foregoing an incremental path to reach the goal, choosing the boil-the-ocean approach. We do need more long term start-from-scratch rethink everything kind of projects; like what VPRI's STEPS project aims to achieve [3]. But there is a lot that can be done to improve the programming experience today, and I don't see enough work in this area. IMO, the latest meaningful improvement in software development tooling was Intellij Idea around 2001 (arguably the functional programming renaissance represents another meaningful improvement, but the real breakthroughs there happened in the 70s). LightTable moving to the Blue plane leaves the PinkPlane unattended.
[1] http://www.adobe.com/technology/projects/content-aware-fill.... [2] https://www.youtube.com/watch?v=UccfqwwOCoY [3] http://www.viewpointsresearch.org/html/writings.php
"As for flow, it works best when there is a specific, narrowly scoped piece of code that must be written. For that work, being in a quiet place free from distraction is ideal. Just don’t stay isolated too long"
I don't see much to disagree with there. I think the point of contention is on what should be the default work environment: an open plan office with "concentration rooms" here and there or individual offices and occasional meetings. I don't believe there will be a definitive answer, it depends on team dynamics and company culture.