<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Zoltan Borsos on Medium]]></title>
        <description><![CDATA[Stories by Zoltan Borsos on Medium]]></description>
        <link>https://medium.com/@borsi?source=rss-bba01e598206------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*livcuWyblUEubOnxuYuY2w.jpeg</url>
            <title>Stories by Zoltan Borsos on Medium</title>
            <link>https://medium.com/@borsi?source=rss-bba01e598206------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:04:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@borsi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Entering the new era —We componentized sensenet ECM for version 7.0]]></title>
            <link>https://medium.com/sensenet/entering-the-new-era-we-componentized-sensenet-ecm-for-version-7-0-bd53796386f?source=rss-bba01e598206------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd53796386f</guid>
            <category><![CDATA[aurelia]]></category>
            <category><![CDATA[refactoring]]></category>
            <category><![CDATA[dotnet]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[components]]></category>
            <dc:creator><![CDATA[Zoltan Borsos]]></dc:creator>
            <pubDate>Wed, 27 Sep 2017 11:41:13 GMT</pubDate>
            <atom:updated>2017-09-27T11:51:12.122Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JoEobjOUyZPSYrafAmaFPQ.jpeg" /><figcaption>Alright. Now, how to put it all back together.</figcaption></figure><p>It’s been a long one year, but we’re nearing the end of the componentization project for sensenet ECM. If you tried to keep up with the progress, what you could see, was a bunch of git repositories, NuGet and npm packages popping up now and again, but you may not be sure what each of them really does. You might be thinking “Okay, you tore the whole thing to pieces, but how the hell does it all fit together?” Fear not.</p><p>I’ll try and break down these components to you, so when you accidentally hop on to our github enterprise page, you won’t feel lost in the forest of repositories.</p><p><em>[[DISCLAIMER: I am not coming up with all this all by myself. People smarter than me, have already written a great description about this </em><a href="http://community.sensenet.com/docs/sensenet-components/"><em>here</em></a><em>. So if you don’t like my style, by all means, hop over there and read everything you can find.]]</em></p><p>If you’re still here, fasten your seatbelts. It’s going to be a long ride. So what’s lurking under the SenseNet enterprise in GitHub?</p><h3>The Core</h3><p><em>The essentials. The alpha, and the omega. What you need to have a powerful content management platform up and running on your premises.</em></p><p><a href="https://github.com/SenseNet/sensenet"><strong>SenseNet/sensenet</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.Services.Install">Current NuGet package</a></p><p>At the very core of sensenet ECM, there’s Sensenet Services. Services is the “Mother of All Components”: you’ll need it, if you want to do anything with sensenet ECM, for it is the heart of the platform.</p><p><em>It contains:</em></p><ul><li>The main Content Repository and dynamic content type system</li><li>A set of built-in basic content types (File, Folder Workspace, ContentList/DocumentLibrary)</li><li>Indexing and Search</li><li>Security</li><li><strong>SenseNet/sn-admin: </strong><em>This handy tool can be your best friend when developing on sensenet ECM. Be sure to get acquainted with each other.</em></li><li><strong>SenseNet/sn-tools: </strong><em>When we face something more than once, it is nice to have a solution at hand the next time we encounter it. We collect our little tools in this repository.</em></li></ul><p>But no UI, whatsoever. You can access the Content Repository inside Services through well defined — you guessed it — services/service entry points, such as the REST API, or WebDav. You can even use the javascript or the .NET client library, which are wrappers for the OData layer.</p><blockquote><em>For detailed install steps please follow </em><a href="http://community.sensenet.com/docs/install-sn-from-nuget/"><em>this link</em></a><em>.</em></blockquote><h3>Extensions</h3><p><em>Everything that makes your life better. Content types, we built for you. Prepackaged business logic in breadcrumbs, with mayo.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dBA9XYui5LDRX0V5.jpg" /><figcaption>Tools make your life better. Use them.</figcaption></figure><p><a href="https://github.com/SenseNet/sn-webpages"><strong>SenseNet/WebPages</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.WebPages.Install">Current NuGet package</a></p><p>WebPages is our good old UI component. When you install it on top of Services, you get a login page and the Content Explorer out of the box. You can build your own pages using the app model and our built-in portlets. Everything you’ll find here is built with <a href="http://asp.net/">ASP.NET</a> WebForms.</p><p><em>To summarize, when you install WebPages, you’ll have:</em></p><ul><li>The Services component (it’s a requirement in the NuGet package)</li><li>The Content Explorer</li><li>A Login page</li><li>Our Built-in Portlets</li></ul><blockquote><em>For detailed install steps please follow </em><a href="http://community.sensenet.com/docs/install-webpages-from-nuget/"><em>this link</em></a><em>.</em></blockquote><p><a href="https://github.com/SenseNet/sn-workspaces"><strong>SenseNet/Workspaces</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.Workspaces.Install">Current NuGet package</a></p><p>Workspaces is a functional component for sensenet ECM, it contains predefined content types for workspaces, you can use for various scenarios. If you only have Services installed (because for whatever reason you don’t want to use WebPages or build your UI using <a href="http://asp.net/">ASP.NET</a> WebForms), you’ll only get the workspace types. If, however, you have WebPages, you’ll also get the related content templates and the whole UI package for Workspaces — build entirely in <a href="http://asp.net/">ASP.NET</a>WebForms.</p><blockquote><em>For detailed install steps, please check </em><a href="http://community.sensenet.com/docs/install-workspaces-from-nuget/"><em>this article</em></a><em>.</em></blockquote><p><a href="https://github.com/SenseNet/sn-workflow"><strong>SenseNet/Workflow</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.Workflow.Install">Current NuGet package</a></p><p>This component integrates the powerful Windows Workflow Foundation into your sensenet ECM. You can use it to build content driven workflows, such as the built-in Approval workflow.</p><p>If you want to build complex business scenarios and processes, Workflow is your go-to component.</p><p><a href="https://github.com/SenseNet/sn-notification"><strong>SenseNet/sn-notification</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.Notification.Install">Current NuGet package</a></p><p>Notifications lets your users subscribe to content changes in the Repository. The notifications are sent via e-mail either in bulk, or immediately.</p><p><a href="https://github.com/SenseNet/sn-taskmanagement"><strong>SenseNet/sn-taskmanagement</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.TaskManagement.Core">Current NuGet package</a></p><p>Task manager is a component you need to install completely separately. It’s for managing long-running background tasks, such as preview generation. But don’t let us set limits for your creativity, the task manager is a powerful tool to run a bunch of tasks in the background on a seperate machine.</p><p>Make sure you read the documentation for Task Management and discover it’s full power.</p><h3>Client libraries</h3><p><em>Manipulate the Content Repository with the magic of client libraries. Build Single Page Applications, compelling UI’s, or WPF desktop apps, all powered with sensenet ECM! Take your pick.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E1wApcNXkuDgNgyj.jpg" /><figcaption>Ask the server for some delicous content you can digest.</figcaption></figure><p><a href="https://github.com/SenseNet/sn-client-js"><strong>SenseNet/client-js</strong></a><strong><br></strong><a href="https://www.npmjs.com/package/sn-client-js">Current npm package</a></p><p>This Javascript (it’s really Typescript, “but who counts” nowadays) library lets you work with the Content Repository by providing a Javascript client API for the main content operations.</p><p>Since we’re talking about a Javascript library, instead of NuGet, you can install it from npm. Once you have a sensenet ECM Services running somewhere, set up CORS and you’re ready to start developing a Single Page Application for example.</p><p>There are several related packages that are in development and that will let you build applications in an even more productive fashion. These are:</p><ul><li><a href="https://github.com/SenseNet/sn-controls-aurelia">sn-controls-aurelia</a></li><li><a href="https://github.com/SenseNet/sn-controls-react">sn-controls-react</a></li><li><a href="https://github.com/SenseNet/sn-redux">sn-redux</a></li></ul><p>The first library contains sensenet ECM UI controls implemented in Aurelia. The second does the same in React, with the exception that our React controls use Redux for a centralized state store, while our Aurelia controls don’t. All of these libraries have the prerequisite of installing sn-client-js.</p><p><a href="https://github.com/SenseNet/sn-client-dotnet"><strong>SenseNet/sn-client-dotnet</strong></a><strong><br></strong><a href="https://www.nuget.org/packages/SenseNet.Client">Current NuGet package</a></p><p>If you fancy using the Content Repository from your .NET application, you can easily do that using the .NET Client for sensenet ECM. The library connects to the REST API and wraps it into a neat C# API. Use it any way you can think of (we think you could build nice WPF apps with it for example)!</p><p>If you have <em>any</em> questions, or feedback, talk to us. You can chat with us on <a href="http://gitter.im/SenseNet/sensenet">Gitter</a>, or send us <a href="http://hello[at]sensenet[dot]com/">e-mails</a>, like in the medieval times.</p><p>This post was <a href="http://community.sensenet.com/blog/2017/09/27/new-sn7-components">originally published on the official Sense/Net Inc. blog</a> on 2017–09–27.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd53796386f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/entering-the-new-era-we-componentized-sensenet-ecm-for-version-7-0-bd53796386f">Entering the new era —We componentized sensenet ECM for version 7.0</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We gave 10% freetime to our developers, this is what we’ve learned so far.]]></title>
            <link>https://medium.com/sensenet/we-gave-10-freetime-to-our-developers-this-is-what-weve-learned-so-far-8251eed3d0ce?source=rss-bba01e598206------2</link>
            <guid isPermaLink="false">https://medium.com/p/8251eed3d0ce</guid>
            <category><![CDATA[freefriday]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[developer-productivity]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[postmortem]]></category>
            <dc:creator><![CDATA[Zoltan Borsos]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 13:04:08 GMT</pubDate>
            <atom:updated>2017-09-14T19:23:05.756Z</atom:updated>
            <content:encoded><![CDATA[<p>Six months have passed since we started our <em>very own</em> ‘Sense/Net 10%’ program, where any employee could assemble a team and work on a precious side-project in 10 percent of their time. We had our project closing TGIF presentation last Friday where every team talked about their experiences — and you wouldn’t believe what happened next!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KKVZ6BMtgucpIjgO.jpg" /></figure><p>Setting aside the subtle clickbait at the end of the intro, we learned <em>a ton</em> in these past six months. Just to recap, these were our goals when <a href="http://community.sensenet.com/blog/2017/06/28/free-friday">we started out</a>:</p><ul><li>Create more vibrant <strong>company culture</strong> by incentivizing cross-team communication.</li><li>Fire up developer <strong>motivation</strong> by letting them work on projects they love and by taking a breath of fresh air from the daily grind.</li><li><strong>Empower</strong> people. Let them <em>own</em> their projects and with them, our company culture, mission and values.</li></ul><h3>Well, did we succeed?</h3><p>Yes… well, sort of. We started this little experiment with three very different projects and teams. The results:</p><ul><li>1 project that is about half complete</li><li>1 project, that has already been completed for 3 months</li><li>and finally, 1 project, that is almost complete</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/0*qNE4DpYzE4FWptpM.gif" /></figure><h3>What went well?</h3><h3>Tangible results</h3><p>When we started Free Friday, we didn’t have a Community Site and our Knowledgebase was falling apart. Now we have both! We also have a logo animation, which works in chrome.</p><h3>Engaging presentations</h3><p>Apart from the fact that almost always the same three guys talked about their projects, these events were pretty good. Even though, the size of the projects and the speed of development differed vastly, everyone could show real progress every month. I was particularly happy, because I could see people, who rarely ever give presentations talk in front of the whole company.</p><h3>Learning, learning, learning</h3><p>After talking with the participants, one thing stood out: people from different teams use vastly different best practices. When we mixed these people, these best practices — more or less — were shared with each other. Not much of a surprise here, but nevertheless… great!</p><h3>What did we learn?</h3><h3>Governance is tricky</h3><p>Without any recommendation for project management techniques or any formal supervision, teams tended to simply omit the ‘management’ part of the project. Which makes sense: if you have <strong>small,</strong> <strong>mature</strong> teams with <strong>clear goals</strong>, you don’t <em>necessarily</em> need managers (<a href="https://m.signalvnoise.com/threes-company-df77db78d1af">at least it works for Basecamp</a>). But Free Friday teams are — by definition — not mature teams and the goals are not always clear for <em>everyone</em>. So chaos can rear its ugly head pretty quickly.</p><h3>Sometimes half-measures are necessary after all</h3><p>Sense/Net Inc. has two, very different company profiles. The <strong>Business Solutions</strong> division has vastly different metrics than <strong>Product Development</strong>. This is why the hardest part of getting this project through the management team was to have PO’s quit obsessing about their teams’ velocities.</p><p>We needed everyone to be on board so Friday afternoons won’t be interfered with, because an extremely important <strong>last minute feature request</strong> lands unexpectedly in the backlog. So we decided to have no half-measures. Either we’re all all-in, or not.</p><p>And even though management was truly fully on board, developers sometimes decided to do their daily work instead, because they felt it was necessary (Hey, we have these responsible guys here. Good on us!). With wonky governance and sometimes-absent team members, there were Friday afternoons when people naturally defaulted back to business as usual.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*OZ2K7M6aRgwCljM0.gif" /></figure><h3>Communication is hard</h3><p>If you’ve ever tried to form your fancy project idea into a digestible format for a very diverse set of people, when even <em>you</em> don’t know, what you really want, then you know what I’m talking about. Developers could really experience what it’s like to be in a stakeholder or leadership position.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/245/0*K3yfQec_nwwdbDO2.gif" /></figure><p>But it’ll never work flawlessly for the first try.</p><h3>What’s next?</h3><p>When I asked “Should we have another iteration of Free Friday?”, the unanimous and immediate answer was ‘absolutely’. In spite of the mentioned shortcomings, people enjoyed participating in the experiment. Communication got a little better and the company got almost two finished products at the end of this six months.</p><p>In the past two weeks people were already asking me, when can they start new projects. I’ve received pretty good project ideas too! So developers are enthusiastic, which is great.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*pMIfxfyhSchus5-P.gif" /></figure><p>The next round is starting in <strong>two weeks</strong> and in the meantime, people can think up new project ideas.</p><p>Just so we don’t commit the same mistakes, we decided to change some of the original rules. These are:</p><ul><li>The next round is <strong>3 months</strong> long, instead of 6. Shorter iteration cycles should gradually produce better end-results.</li><li><strong>Team sizes</strong> can range from <strong>1 to 3</strong> people. The reason for at least 2-person teams was to incentivize collaboration between different teams. We realized though, that this way small, creative projects fall out of the basket. They’ll get their chance now.</li><li>People can move from one team to another within a cycle, given the proper reasons. Right now we don’t see why this should cause any troubles</li><li>Presentations are every <strong>2 week</strong>. That’s right, you have to talk <em>even more</em>.</li><li>Free Friday is still on Friday afternoon. But if you have a Sprint Review and you talk with your FF and Business Solutions team, you can move your weekly 10% to a more appropriate time slot.</li></ul><p>But otherwise everything stays the same. The type of the projects, the need for transparency and the frequent communication stays. My personal dream is that in time, most of the rules will wither away and this group dynamic we now call as ‘Free Friday’ will just melt into the company culture, enriching it with awesomeness.</p><p>See you in 3 months!</p><p>This post was originally published on the<a href="http://community.sensenet.com/blog/2017/09/13/freefriday-aftermath"> official community blog of Sense/Net Inc.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8251eed3d0ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/we-gave-10-freetime-to-our-developers-this-is-what-weve-learned-so-far-8251eed3d0ce">We gave 10% freetime to our developers, this is what we’ve learned so far.</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is a headless cms anyway?]]></title>
            <link>https://medium.com/sensenet/what-is-a-headless-cms-anyway-a10f610cfe9e?source=rss-bba01e598206------2</link>
            <guid isPermaLink="false">https://medium.com/p/a10f610cfe9e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[content-management-system]]></category>
            <category><![CDATA[restful-api]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Zoltan Borsos]]></dc:creator>
            <pubDate>Wed, 05 Jul 2017 10:20:18 GMT</pubDate>
            <atom:updated>2017-07-05T10:20:18.873Z</atom:updated>
            <content:encoded><![CDATA[<p>The term ‘headless cms’ has been rising in popularity for a while now. But why the hype and what is it all about?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UR3AeHf2SXnONiOy3ezavg.jpeg" /><figcaption>Plunge headfirst into the sea of ECMS’s</figcaption></figure><h3>What is a headless CMS?</h3><p>We’ll get to that. But first, it’s worth mentioning how traditional “monolithic” cms’s work. Wordpress or Drupal are usually included in this category. At monolithic cms’s, the modal layer is tightly coupled with the view, and the creators of the platform provide you with a templating engine with which you can implement your frontend. So in this model you’d have:</p><ul><li>a Database at the “bottom”, where you store your content</li><li>an App, with a UI that lets you <a href="https://en.wikipedia.org/wiki/Create,_read,_update_and_delete">Create, Read, Update and Delete</a> this content</li><li>and a View layer which displays the content (usually by using templates)</li></ul><p>Older versions of <a href="https://www.sensenet.com/product">sensenet ECM</a> are also following this philosophy, although the platform is more geared towards enterprise features, such as <a href="http://community.sensenet.com/docs/versioning-and-approval">content versioning</a> and <a href="http://community.sensenet.com/docs/workspace">collaboration</a>. Thus, the ‘E’ in ECM is for <strong>Enterprise</strong>.</p><p>This is why you could do something like this in <a href="http://community.sensenet.com/docs/how-to-install-sn6/">sensenet 6.x</a>, or using <a href="https://github.com/SenseNet/sn-webpages">sn-webpages 7.x</a>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b0ed9eb03e345d9aa4e8114be7a711bb/href">https://medium.com/media/b0ed9eb03e345d9aa4e8114be7a711bb/href</a></iframe><p>In a headless CMS (or ECMS for that matter), though, the backend does not care about how the content is displayed. It just returns with the data needed for the frontend through a RESTful API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/973/0*yZmbtBtylAihzinD.png" /><figcaption>fig 2. ~ Traditional (coupled or monolithic CMS) model vs. Headless CMS</figcaption></figure><h3>So is sensenet ECM a headless or a coupled CMS?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*y8ZkpUzukIXz3nRS.gif" /></figure><p>As mentioned earlier, using sn-webpages, you can have a full-featured ECMS solution, complete with a built-in UI. We are also working on a <strong>new</strong> UI, using <a href="https://github.com/SenseNet/sn-controls-react">React</a> and <a href="https://github.com/SenseNet/sn-controls-aurelia">Aurelia</a> while fully utilizing <a href="http://community.sensenet.com/docs/built-in-odata-actions-and-functions/">sensenet ECM’s OData layer</a>, which provides a complete, flexible and extendable <a href="http://community.sensenet.com/docs/odata-rest-api/">RESTful API</a>.</p><p>In the meantime, you can either start writing your own library to latch on the OData endpoints of a sensenet ECM instance at hand, <strong>or</strong> you can try out our <a href="https://github.com/SenseNet/sn-client-js">fabulous and open source sn-client-js, the javascript client library for sensenet</a>.</p><p>In the end, what you get is something like this[1]:</p><p><strong>After installing our library from npm, you can import it</strong> and connect to your sensenet ECM instance.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/67c413f6428a0d80fcd73b9a556b1f84/href">https://medium.com/media/67c413f6428a0d80fcd73b9a556b1f84/href</a></iframe><p><strong>Once done, you can start working with content</strong> e.g. fetching them for using the results as a sn-client-js Collection</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/729d1d5b85f4f51b58378f3dbdb4e236/href">https://medium.com/media/729d1d5b85f4f51b58378f3dbdb4e236/href</a></iframe><p><strong>The collection is ready, so you can start working with your favourite framework to render the article list.</strong></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/a8d5cb76073c38809db5e06c5b457a6c/href">https://medium.com/media/a8d5cb76073c38809db5e06c5b457a6c/href</a></iframe><p>As simple as that. We are at the beginning of our roadmap and we need your feedback in making a better ECMS development platform. So feel free to chime in either through <a href="http://community.sensenet.com/blog/2017/07/05/helloATsensenetDOTcom">e-mail</a>, <a href="https://gitter.im/SenseNet/sensenet">gitter</a> or by sending a <a href="http://i.imgur.com/yldRjme.gif">homing pigeon</a>. We are eager to hear your voice.</p><p>[1]: You can achieve a similar experience using the <a href="https://github.com/SenseNet/sn-client-dotnet">.NET client for sensenet ECM.</a></p><p><em>Disclaimer: Since I am not a developer, my initial code examples were not as fabulous as they are now. Many thanks to @</em><a href="https://github.com/tusmester"><em>tusmester</em></a><em> and @</em><a href="https://github.com/herflis"><em>herflis</em></a><em> for providing me with meaningful snippets.</em></p><p><em>This post was originally published on </em><a href="http://community.sensenet.com/blog/2017/07/05/what-is-a-headless-cms"><em>the official blog of Sense/Net Inc.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a10f610cfe9e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/what-is-a-headless-cms-anyway-a10f610cfe9e">What is a headless cms anyway?</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Free friday for all — Chapters in Sense/Net]]></title>
            <link>https://medium.com/sensenet/free-friday-for-all-chapters-in-sense-net-14df9e51546?source=rss-bba01e598206------2</link>
            <guid isPermaLink="false">https://medium.com/p/14df9e51546</guid>
            <category><![CDATA[empowering-innovation]]></category>
            <category><![CDATA[chapters]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[freefriday]]></category>
            <dc:creator><![CDATA[Zoltan Borsos]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 12:31:02 GMT</pubDate>
            <atom:updated>2017-06-28T13:02:10.218Z</atom:updated>
            <content:encoded><![CDATA[<p>In their <a href="https://abc.xyz/investor/founders-letters/2004/ipo-letter.html">2004 IPO letter</a>, founders Larry Page and Sergey Brin highlighted their idea of the famous “Google 20%”. A lot of time has passed since then and the legend faded too: is it really 20% of their time, or is it more like “Google 120%”?</p><p>Nonetheless, we wanted to empower our people so we decided to give it — or at least <strong>a</strong> version of it — a go.</p><blockquote><em>We encourage our employees, in addition to their regular projects, to spend 20% of their time working on what they think will most benefit Google. This empowers them to be more creative and innovative. Many of our significant advances have happened in this manner. For example, AdSense for content and Google News were both prototyped in “20% time.” Most risky projects fizzle, often teaching us something. Others succeed and become attractive businesses.</em></blockquote><p>They wrote. It almost sounds too good to be true: our people do what they think is best for us, and it truly gets better. It is always important to remind ourselves before getting overly excited about things like this, that <a href="https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb"><em>we are not Google</em></a>. So before rushing to the solution, we need to think about our own corporate structure, and problems we need to be solved.</p><h3>How Sense/Net Inc. works</h3><p>Sense/Net Inc. — the company behind sensenet ECM — has two products. One actual product (sensenet ECM) and a solution integrator service: since we know our product the best, we can create unique solutions for companies all around the world (we also do training and quite a lot of support, but let’s just consider these parts of one or both of the products I just mentioned).</p><p>This results in teams that not just work on different projects, they do <strong>different kinds of things</strong>. In time, people end up with vastly different know-hows and knowledge levels. It is hard to admit, but <em>sometimes</em> there are multiple solutions for the same problem. Or worse, there are the same solutions implemented several times for the same problem.</p><h3>The problems</h3><h4>Lacking Communication</h4><p>This all comes down to communication. As a small company, communication <em>should</em> not be a problem. However, since there are a lot of demanding projects, teams can become project-silos, working hard on solutions for large periods of time, without having a direct contact with any other team. Team members rarely mix, so over time, company culture can degrade.</p><h4>Fading Motivation</h4><p>Working on repetitive business solutions can become demotivating after a while. Software development supposed to be a <em>creative</em> craft, so solving client problems day after day can make Jack a dull boy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_qBvPbhXkiDhsxEg.png" /></figure><h4>No Empowerment</h4><p>It is a good feeling to <em>really</em> own a project. If it is <em>yours</em>, you’ll work on it all the time (at home, at night, in the morning), because it is your brainchild. It is your responsibility. Our developers are our cleverest people in our company. Some of them have pretty good ideas on what should we be working on, so our organization would benefit the most of the work done. So why not let them?</p><h3>The possible solution</h3><h4>Let them</h4><p>Let them come up with ideas and realize them during work hours. Let them form teams and incentivize them to finish their projects. Let them try different team roles and techniques. Let them build their tools and make sensenet great. Help them form bonds with each other and learn the viewpoint of others. Rebuild our network of connections inside the company.</p><h4>The rules</h4><p>To help start this endeavor, all parties (executives, managers, PO’s, scrum masters, developers) needed to agree on the rules of the game. These rules are:</p><ul><li>The time is “sacred”</li></ul><blockquote>That is, first of all it is important that “free-friday” time is sacred time: otherwise, the 10 or 20% can be overwritten by any enthusiastic PO so “we can just fix one more bug this friday afternoon” or “can we just add this one more feature here please”.</blockquote><ul><li>Working in these projects is not <em>mandatory</em></li></ul><blockquote>You can continue working on anything work-related during ‘free-friday’.</blockquote><ul><li>Anyone can create a team</li></ul><blockquote>You just need to be more than one person. One of the goals is to make communication better — you know yourself, now you may get to know other people. If the other ones are from different teams, it is all for the better.</blockquote><ul><li>You will need a project you think is most beneficial for Sense/Net, the company</li></ul><blockquote>If you think it’s a tool, or a new module for the platform, it’s great. If you think the thing you’ll build will help us communicating the awesomeness of us, it’s great too! Tell us all about your ideas and on how you plan on implementing them.</blockquote><ul><li>Transparency is key</li></ul><blockquote>Don’t hide in your team-cave with your new found team-friends for 6 months. You need to get out and tell us about what you’re going through. Every month, we use a TGIF so you can tell everybody about the hardships of forming a team and communicating an idea. You can show everyone, how you conquered a problem or how you failed (which happens all the time, and is okay most of the time if we learn from our mistakes).</blockquote><h3>It’s happening</h3><p>We started this project with a kickoff presentation, where we gave people time to come up with project ideas. This was not very hard, since practically everyone has a long-cherished brainchild in the back room of their mind.</p><p>After vetting these ideas, there were 3 that had enough people and reasonable planning behind (we are a small company after all :) ).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/312/0*eosUmtd5VyQVUG0q.gif" /></figure><p>These three (a knowledge base for our company, a reposync tool for making our developers’ lives easier, and our new <a href="http://community.sensenet.com/">community site</a>) are progressing quite well. Since “Transparency is key”, I’m sure you’ll hear about them soon enough. :)</p><h3>Is it any good?</h3><p>All three pilot projects are progressing reasonably since our kickoff presentation. We have an internal virtual scrum master, who helps these teams gel and work more efficiently. The first two project status TGIF’s were also promising and it seems that developers like the authority they get in their side projects.</p><h4>But is it any good for the company?</h4><p>Definitely. It wasn’t possible to allocate resources for either a knowledgebase or a community site project. The knowledgebase serves as our internal repository of thoughts and resources and helps keeping together our company-hivemind. This community site since became of strategic importance. We need it for external communication, for storing our documentation and for community building. There’s also the reposync tool, which boosts business solution teams’ productivity tremendously.</p><h4>What’s next?</h4><p>We have three months left of this pilot. We plan to organize a Fedex Day type event at the end to celebrate the successes and ponder on the failures. Until then, we’ll keep you posted on these projects.</p><p><a href="http://community.sensenet.com/blog/2017/06/28/free-friday"><em>This post was originally published on the official blog of Sense/Net Inc.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14df9e51546" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sensenet/free-friday-for-all-chapters-in-sense-net-14df9e51546">Free friday for all — Chapters in Sense/Net</a> was originally published in <a href="https://medium.com/sensenet">sensenet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>