<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>hibNet</title><link>http://www.hibnet.org/</link><description>I don't talk much, I don't think less.</description><atom:link href="http://www.hibnet.org/rss.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2026 &lt;a href="mailto:nicolas.lalevee@hibnet.org"&gt;Nicolas Lalevée&lt;/a&gt; 
&lt;a rel="license" href="https://creativecommons.org/licenses/by-nc-sa/4.0/"&gt;
    &lt;img alt="Creative Commons License BY-NC-SA" style="border-width:0; margin-bottom:12px;"
        src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png"&gt;
&lt;/a&gt;
</copyright><lastBuildDate>Wed, 01 Apr 2026 11:40:41 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Experimenting around React's scalability</title><link>http://www.hibnet.org/blog/experimenting-around-react-scalability/</link><dc:creator>Nicolas Lalevée</dc:creator><description>&lt;div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;Writing backend code has always been my preference because it allows more structured code, since backend often means Java in my industry, the web. On the other hand frontend coding has always been a pain because of the mess. Javascript may be the culprit, but probably more because it allows to be messy more than being messy itself. Then one day I tested Angular (the v1) and I had the wow effect: first time I felt like an engineer writing Javascript code. Then appeared React: awesome, about same idea but just a library not a full framework. Our team at &lt;a href="http://www.scoop.it/"&gt;Scoop.it&lt;/a&gt; adopted it and embraced it.&lt;/p&gt;&lt;/div&gt;
&lt;div class="paragraph"&gt;&lt;p&gt;We embraced it so much that we felt the pain in writing big React pages. Raw React doesn’t scale well. People already faced this scalability issue. They came with the idea of Flux (thank you people at Facebook to have shared it with us).&lt;/p&gt;&lt;/div&gt;
&lt;div class="paragraph"&gt;&lt;p&gt;While reading about Flux I started designing a way of managing the state. Later some smart guys of our team dived and fell in love of Redux, an open source implementation of Flux. I learned from them and I made improvement to my design. Here is the story.&lt;/p&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://www.hibnet.org/blog/experimenting-around-react-scalability/"&gt;Read more…&lt;/a&gt; (15 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><guid>http://www.hibnet.org/blog/experimenting-around-react-scalability/</guid><pubDate>Fri, 12 Jan 2018 07:30:57 GMT</pubDate></item><item><title>Parallel Universe</title><link>http://www.hibnet.org/blog/parallel-universe/</link><dc:creator>Nicolas Lalevée</dc:creator><description>&lt;div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;Lately I saw a lot of excitement around writing asynchronous code, non blocking, lock free, etc… This is good as we are moving towards more parallelized/concurrent softwares and libraries. There are nice performance improvements ahead. But I fear that we are going into having code hard to understand and therefore to debug.&lt;/p&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://www.hibnet.org/blog/parallel-universe/"&gt;Read more…&lt;/a&gt; (4 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><guid>http://www.hibnet.org/blog/parallel-universe/</guid><pubDate>Fri, 04 Oct 2013 14:30:57 GMT</pubDate></item><item><title>Tweaking the search</title><link>http://www.hibnet.org/blog/tweaking-search/</link><dc:creator>Nicolas Lalevée</dc:creator><description>&lt;div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;&lt;a href="http://www.hibnet.org/blog/you-know-for-search"&gt;Setting up a search engine&lt;/a&gt; in one thing, but to make it actually work, in the human sense, is another story. Having a search which basically does a grep on all your content is the bare minimum you can do, but what makes Google awesome is that when you search something, you find &lt;em&gt;quickly&lt;/em&gt; &lt;em&gt;good&lt;/em&gt; content. When you search something, you should find &lt;em&gt;good&lt;/em&gt; results, and the good results &lt;em&gt;first&lt;/em&gt;. Here some of the things we did to make the Scoop.it search looks good.&lt;/p&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://www.hibnet.org/blog/tweaking-search/"&gt;Read more…&lt;/a&gt; (6 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><guid>http://www.hibnet.org/blog/tweaking-search/</guid><pubDate>Fri, 13 Sep 2013 12:43:13 GMT</pubDate></item><item><title>You know, for search</title><link>http://www.hibnet.org/blog/you-know-for-search/</link><dc:creator>Nicolas Lalevée</dc:creator><description>&lt;div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;As soon as you start having a good amount of data, browsing them is not anymore a solution and you need a search engine. It happened to us some time ago at &lt;a href="http://www.scoop.it"&gt;Scoop.it&lt;/a&gt;. We are pretty happy with what we put in place almost 2 years ago. Let’s revisit the story.&lt;/p&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://www.hibnet.org/blog/you-know-for-search/"&gt;Read more…&lt;/a&gt; (8 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><guid>http://www.hibnet.org/blog/you-know-for-search/</guid><pubDate>Sat, 13 Jul 2013 14:27:56 GMT</pubDate></item><item><title>It's time to share</title><link>http://www.hibnet.org/blog/its-time-share/</link><dc:creator>Nicolas Lalevée</dc:creator><description>&lt;div&gt;&lt;div class="paragraph"&gt;&lt;p&gt;Now that have learned and practiced software engineering a good amount of time, I think I can share back some of my experiences and discuss with you about some hopfully interesting ideas.&lt;/p&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://www.hibnet.org/blog/its-time-share/"&gt;Read more…&lt;/a&gt; (1 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><guid>http://www.hibnet.org/blog/its-time-share/</guid><pubDate>Mon, 24 Jun 2013 06:27:22 GMT</pubDate></item></channel></rss>