FEED Validator

Sorry

This feed does not validate.

• line 5, column 16: language must be an ISO-639 language code: en,de [help]

  	<language>en,de</language>
                  ^

• line 7, column 1: Undefined channel element: pubdate [help]

  	<pubdate>Thu, 20 Jul 2017 23:35:32 +0800</pubdate>
   ^

• line 91, column 77: link must be a full and valid URL: 2017/07/from-blogsphere-to-a-static-site-part-5-comment-front-end.html (10 occurrences) [help]

  	<link>2017/07/from-blogsphere-to-a-static-site-part-5-comment-front-end.htm ...
                                                                               ^

• line 92, column 25: Invalid email address: Stephan H Wissel (10 occurrences) [help]

  	<author>Stephan H Wissel</author>
                           ^

• line 93, column 39: guid must be a full URL, unless isPermaLink attribute is false: 7380F00B6085195048258163005240F6 (10 occurrences) [help]

  	<guid>7380F00B6085195048258163005240F6</guid>
                                         ^

• line 94, column 26: pubDate must be an RFC-822 date-time: 2017-07-20 10:58 (10 occurrences) [help]

  	<pubDate>2017-07-20 10:58</pubDate>
                            ^

In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 8, column 145: Self reference doesn't match document location [help]

  ... //feeds.feedburner.com/Wisselnetfeed" /><feedburner:info xmlns:feedburne ...
                                               ^

• line 90, column 219: description should not contain relative URL references: /blog/2017/05/from-blogsphere-to-a-static-site-part-4-comment-backend.html (13 occurrences) [help]

  ... ) and the respective JS files:&lt;/p&gt;</description>
                                               ^

Source: https://feeds.feedburner.com/Wisselnetfeed

1. <?xml version="1.0" encoding="UTF-8"?>
2. <?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss version="2.0"><channel><title>wissel.net Usability - Productivity - Business - The web - Singapore and Twins</title>
3. <link>https://wissel.net/blog/stories.rss</link>
4. <description>Thoughts, Insights and Opinions of Stephan H. Wissel. Topics included: IBM Lotus Notes and Domino, IBM Websphere, other IBM Lotus stuff,  J2EE, .Net, Software Archtecture, Personcentric Development, Agile Software, SDLC, Singapore and my Twins</description>
5. <language>en,de</language>
6. <copyright>(C) 2003 - 2017 Stephan H. Wissel, All rights reserved</copyright>
7. <pubdate>Thu, 20 Jul 2017 23:35:32 +0800</pubdate>
8. <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/Wisselnetfeed" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="wisselnetfeed" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item><title>From Blogsphere to a Static Site (Part 5) - Comment front-end</title>
9. <description>&lt;p&gt;In &lt;a href="/blog/2017/05/from-blogsphere-to-a-static-site-part-4-comment-backend.html"&gt;Part 4&lt;/a&gt; I described the comment backend. This installment sheds a light on the comment front-end.&lt;/p&gt;
10. <p>Comments can be tricky. One lesson I learned early: When your comment form is standard HTML form, it attracts spam like a light bulb attracts moths. So the requirement were:</p>
11. <ul>
12. <li>The original blog entry should not contain any HTML form. It should be loaded on a button click using JavaScript. Nota bene: this isn't hide/show, but actual manipulation of the DOM</li>
13. <li>The dynamic form shall not contain a POST URL, but submission should be in JavaScript - keeps a lot of the scumbags out already</li>
14. <li>Submission should be secured with a Captcha</li>
15. <li>Some formatting should be allowed. I opted for a Markdown editor with preview capabilities</li>
16. </ul>
17. <p>The first component is the placeholder for the existing comments and the button showing the comment form:</p>
18. <pre class="brush: html">
19. <a name="comments"></a>
20. {{^commentsclosed}}
21. <div class="well well-raised" style="text-align : center">
22.  <button class="btn btn-lg btn-info" data-toggle="collapse" data-target="#commentform_{{UNID}}" type="button">
23.    Add your comment...  <span class="glyphicon glyphicon-comment"></span>
24.  </button>
25. </div>
26. <div id="commentform_{{UNID}}" class="collapse"></div>
27. {{/commentsclosed}}
28. <div class="well well-raised">
29.  <h4>Comments</h4>
30.  <ol id="commentList">
31.    {{#comments}}
32.    <li>
33.      {{#gravatarURL}}<img src="{{.}}" class="gravatarimg" /> {{/gravatarURL}} posted by <b>{{author}}</b> on <i>{{createdString}}</i>:
34.      <br /> {{& comment}}
35.      <hr style="clear : both" />
36.    </li> {{/comments}} {{^comments}}
37.    <li id="nocomments">
38.      <h5>No comments yet, be the first to comment</h5>
39.    </li>
40.    {{/comments}}
41.  </ol>
42. </div>
43. </pre>
44. <p>The second component is the comment form, implemented as mustache template - one of the reasons I picked Mustache: runs on the server and the client in tons of languages</p>
45. <pre class="brush: html">
46. <form title="Comment form for blog discussion" onSubmit="return addComment(this,'{{recaptchaid}}','{{parentId}}')" class="form-vertical well well-raised">
47.  <fieldset>
48.    <legend>Add your comment</legend>
49.    <p>Please note: <b>Comments without a valid and working eMail address will be removed.</b>
50.      <br /> This is my site, so I decide what stays here and what goes.</p>
51.     <div class="control-group" id="commentcontrol">
52.      <label class="control-label" for="Commentor">Name (required, published)</label>
53.      <div class="controls">
54.        <input class="input-xlarge focused" id="Commentor" size="30" accesskey="n" name="nameAuthor" />
55.      </div>
56.      <label class="control-label" for="Email">eMail (required, not published)</label>
57.      <div class="controls">
58.        <input type="eMail" class="input-xlarge focused" id="Email" size="30" accesskey="n" name="txtEmail" placeholder="A working eMail please!" />
59.      </div>
60.      <label class="control-label" for="webSite">URL (optional)</label>
61.      <div class="controls">
62.        <input type="url" class="input-xlarge" id="webSite" size="30" accesskey="n" name="txtWebSite" />
63.      </div>
64.      <div class="controls">
65.        <div id="wmd-panel" class="wmd-panel">
66.          <table style="width : 100%" border="0">
67.            <tr>
68.              <td style="width : 50%; vertical-align : top">
69.                <label class="control-label" for="wmd-input">Your Comment (Use markdown like <a href="//stackoverflow.com/editing-help" target="_blank">Stackoverflow</a>)</label>
70.                <div id="wmd-button-bar"></div>
71.                <textarea class="wmd-input" id="wmd-input" name="Body"></textarea>
72.              </td>
73.              <td style="width : 50%; vertical-align : top">
74.                <label class="control-label">Preview</label>
75.                <div id="wmd-preview" class="wmd-panel wmd-preview"></div>
76.              </td>
77.            </tr>
78.          </table>
79.        </div>
80.      </div>
81.      <div class="controls" id="captchadiv">Captcha here</div>
82.      <div class="form-actions">
83.        <button id="commentsubmit" type="submit" class="btn btn-primary btn-large">Post your comment</button>
84.      </div>
85.    </div>
86.    <div class="alert alert-block" id="alertContainer" style="display : none">One moment please, submitting comment...</div>
87.  </fieldset>
88. </form>
89. </pre>
90. &lt;p&gt;The whole mechanism gets to work with just a few jQuery JavaScript functions (Vanilla JS would work too, but I had JQuery already for the social buttons, so I reused that) and the respective JS files:&lt;/p&gt;</description>
91. <link>2017/07/from-blogsphere-to-a-static-site-part-5-comment-front-end.html</link>
92. <author>Stephan H Wissel</author>
93. <guid>7380F00B6085195048258163005240F6</guid>
94. <pubDate>2017-07-20 10:58</pubDate>
95.  
96. </item>
97. <item><title>Ownership flow of customer community created cases</title>
98. <description>&lt;p&gt;In a previous entry I &lt;a href="/blog/d6plinks/SHWL-APBH4Q"&gt;mapped out&lt;/a&gt; sharing abilities the Salesforce platform is capable of.&lt;/p&gt;
99. <p>In this entry I will put these capabilities to practial use. The scenario starts with a customer logging into the customer community and raising a ticket. Client representative, the partner and support staff need/want access to the case. The case needs to flow along the same processing as cases created by other means (call, email, IoT). The following diagram explains the flow (click for a <a href="/blog/images/2017/CustomerCreatedCases.png">larger version</a>):</p>
100. <a href="/blog/images/2017/CustomerCreatedCases.png" alt="Click to get a bigger version"><img src="/blog/images/2017/CustomerCreatedCases640.jpg" border="0" alt="Customer Portal Created Cases Ownership flow" /></a>
101. &lt;p&gt;The diagram has been rendered using &lt;a href="https://www.websequencediagrams.com/"&gt;Websequencediagrams&lt;/a&gt; based on a plain text file:&lt;/p&gt;</description>
102. <link>2017/07/ownership-flow-of-customer-community-created-cases.html</link>
103. <author>Stephan H Wissel</author>
104. <guid>83FFC90480FAC1EB4825815F004C494B</guid>
105. <pubDate>2017-07-16 09:53</pubDate>
106.  
107. </item>
108. <item><title>Using FontAwesome in your VisualForce pages</title>
109. <description>&lt;p&gt;I'm a big fan of &lt;a href="http://fontawesome.io/"&gt;Font Awesome&lt;/a&gt; (including backing &lt;a href="https://fontawesome.com/"&gt;Version 5&lt;/a&gt;). It allows to add icons without the overhead of loading tons of small graphic files. In a recent internal project I had to integrate FontAwesome into a Salesforce VisualForce page&lt;/p&gt;
110. <h2 id="installing-fontawesome">Installing FontAwesome</h2>
111. <p>In theory you could load the font from a CDN. However based on security settings this might or might not work. So I decided to add FontAwesome as resource to my project:</p>
112. <ol>
113. <li><a href="http://fontawesome.io/assets/font-awesome-4.7.0.zip">Download FontAwesome 4</a>. Or support the team and use <a href="https://fontawesome.com/">Version 5</a></li>
114. <li>Add the zip file as static resource to your setup:<br /> <img src="/blog/images/2017/SFFAStatic.png" alt="Static Resource for FontAwesome" /></li>
115. <li>Make sure you have set the cache control to <code>public</code>, so the font doesn't need download after first use.</li>
116. </ol>
117. <h2 id="adding-to-the-visualforce-page">Adding to the VisualForce Page</h2>
118. <p>The font gets added using a stylesheet that is included in the zip file added as a resource in the previous step. the <code>apex:stylesheet</code> element takes care of that. The only catch: the zip file is internally "expanded" OS/X style with the file name (sans extension) as directory name. So the tag needs to look like this:</p>
119. <pre><code>  <apex:stylesheet value="{!URLFOR($Resource.fontawesome,'/font-awesome-4.7.0/css/font-awesome.css')}"/></code></pre>
120. <h2 id="using-icons">Using Icons</h2>
121. <p>This follows the standard approach: you create an empty <code><i></code> element and use the class property to specify icon and options. Like this:</p>
122. <pre><code>  <i style="color: red" class="fa fa-user-circle fa-2x" aria-hidden="true"></i></code></pre>
123. <p>Make sure you have a look at the <a href="http://fontawesome.io/icons/">full selection</a> of icons available.</p>
124. &lt;p&gt;As usual: YMMV&lt;/p&gt;</description>
125. <link>2017/07/using-fontawesome-in-your-visualforce-pages.html</link>
126. <author>Stephan H Wissel</author>
127. <guid>97E8ED82940D30104825815F0045EF13</guid>
128. <pubDate>2017-07-14 08:43</pubDate>
129.  
130. </item>
131. <item><title>Salesforce Community License Overview</title>
132. <description>&lt;p&gt;To facilitate collaboration across corporate boundaries, Salesforce offers &lt;b&gt;Salesforce Communities&lt;/b&gt;. The licence for communities come in three flavours: customer community, customer community plus and partner community. There are similarities and differences between the entitlements.&lt;/p&gt;
133. <p>The biggest difference can be seen between customer community and customer community plus. There's a simple rationale behind it: a customer community account uses simplified sharing access, so the computational load to determine access of potentially millions of users stays reasonable and easy to grasp for administrators:</p>
134. <a href="/blog/images/2017/CommunityLicenses.jpg" alt="Click for a bigger version"><img src="/blog/images/2017/CommunityLicenses640.jpg" border="0" alt="Community License Overview" /></a>
135. &lt;p&gt;All licences, full Salesforce or one of the community licence types, access the same data, in the confines of the entitlements. So it's NOT different products, just different permissions on the Salesforce platform.&lt;/p&gt;</description>
136. <link>2017/07/salesforce-community-license-overview.html</link>
137. <author>Stephan H Wissel</author>
138. <guid>9B77F8952FFBAA284825815F004B1D1E</guid>
139. <pubDate>2017-07-10 09:40</pubDate>
140.  
141. </item>
142. <item><title>Sharing is caring - Salesforce edition</title>
143. <description>&lt;p&gt;I like &lt;a href="/blog/2014/02/domino-development-back-to-basics-part-6-better-safe-than-sorry-security.html"&gt;declarative security&lt;/a&gt; to give access exactly to the extend a user requires. When learning Salesforce, I discovered to my delight the portfolio of possibilities to tailor access. With great powers, as we know, come great responsibilities. Learning the Salesforce lingo can be quite daunting. So here is my little overview:&lt;/p&gt;
144. <a href="/blog/images/2017/SalesforceSharingTerminology.jpg"><img src="/blog/images/2017/SalesforceSharingTerminology640.jpg" border="0" alt="Salesforce Sharing Terminology, click for full size" /></a>
145. <ul>
146. <li>Access to data in Salesforce is based on two principles: everything is <b>owner based</b> and a generally restricted access can be <b>extended</b> for given conditions, but not limited. This single vector of access makes systems cleaner that the ability to add and remove privileges based on conditions. It avoids the need to resolve conflicts where condition 1 gives access, while condition 2 would remove it. These conflict solution rules are a security flaw in waiting (prime vector for human error). Nevertheless access in Salesforce need to be well planned (How much does any role need to see: give to little and you invite data duplicates, give too much and you increase leakage risks) - How to plan is another story for another time</li>
147. <li>Access has 3 element: access to objects (that would be access to classes in OO), access to records (instances of a class) and fields (properties of a class instance) </li>
148. <li>Computation starts from the organization wide settings, which are the most restrictive settings for a given organisation and then gets extended with various means (see image above)</li>
149. <li>There's a general distinction between internal access and access via a community. This reflects the need to be able to interact with customers, suppliers and partners in a controlled fashion</li>
150. <li>Owner based: I've seen this quite often: data exists, gets used, but nobody wants to own it, the owner has left or data gets inaccessible when the owner gets deleted. All this issues don't happen in Salesforce since no object data can exist that doesn't have an owner and owner transfer capability is baked into the platform (even rule based, but that's another story for another time)</li>
151. <li>Hierarchical: access rules know the role and reporting hierarchy. So access can be granted to a user and her entire reporting hierarchy including subordinates etc. Quite extensive possibilities worth exploring</li>
152. </ul>
153. &lt;p&gt;As usual YMMV&lt;/p&gt;</description>
154. <link>2017/07/sharing-is-caring-salesforce-edition.html</link>
155. <author>Stephan H Wissel</author>
156. <guid>4DB48552876449C84825815F0046B560</guid>
157. <pubDate>2017-07-07 08:52</pubDate>
158.  
159. </item>
160. <item><title>Meeting a CxO</title>
161. <description>&lt;img src="/blog/images/2017/MeetingaCxO.jpg" border="0" alt="Meeting a CxO" /&gt;
162. <br /> These are my notes on a role play we did in Salesforce to better cater to successful CxO meetings. Most of the topics do apply to
163. &lt;b&gt;any&lt;/b&gt; meeting, so no surprises here. We had actual CxO as participants. They shared that the most common item wanting is clear meeting agendas with outcomes, including them being time managed during the meeting. Second in line were unclear outcomes and not asking for a follow-up meeting.</description>
164. <link>2017/06/meeting-a-cxo.html</link>
165. <author>Stephan H Wissel</author>
166. <guid>AF131F1CDCDDE8324825813900082175</guid>
167. <pubDate>2017-06-08 09:28</pubDate>
168.  
169. </item>
170. <item><title>From Blogsphere to a Static Site (Part 4) - Comment backend</title>
171. <description>&lt;p&gt;The blog needed a comment function. While there are social options around (Facebook, &lt;a href="https://disqus.com/"&gt;Disqus&lt;/a&gt; etc), I decided I want to roll my own. Partly because I want tighter control and partly, well, because I could. My comment backend would:&lt;/p&gt;
172. <ul>
173. <li>Provide a REST API to create comments in a JSON structure. The comment body will be <a href="https://daringfireball.net/projects/markdown/syntax">Markdown</a>. Reading would provide comments in ready to use HTML (I hear howling from the API crowd). No delete or update functionality</li>
174. <li>Cleanup content considered harmful (code injection) and optional sport Captcha</li>
175. <li>Store all content in a NoSQL database, in my case CouchDB (or Cloudant with its 20G free plan)</li>
176. <li>Cache all queries for comment in an online cache to limit calls to the database</li>
177. <li>Initially run on Domino, later on liberty or the raw JVM</li>
178. <li>Initially also update Domino using a web service - so during transition no comments would get lost</li>
179. </ul>
180. <p>In its initial incarnation the Comment servlet is a OSGi plugin that listens to the <code>/comments</code> URL implemented as Wink servlet. So the class of interest is the one defining the service. We have one method for post, one for get and a helper function</p>
181. <pre class="brush: java">
182. /**
183. * Wink implementation of Comment service
184. */
185. @Workspace(workspaceTitle = "Blog Comments", collectionTitle = "Create or display comments")
186. @Path(value = "/comments")
187. @Produces(MediaType.TEXT_HTML)
188. @Consumes(MediaType.APPLICATION_JSON)
189. public class CommentService extends CommentResponse {
190.  
191.    private final Logger logger = Logger.getLogger(this.getClass().getName());
192.  
193.    @POST
194.    public Response createComment(@Context HttpServletRequest request) {
195.        final Monitor mon = MonitorFactory.start("CommentService#createComment");
196.        String result = "Sorry I can't process your comment at this time";
197.        ResponseBuilder builder = Response.ok();
198.  
199.        try {
200.            InputStream in = request.getInputStream();
201.            BlogComment comment = BlogComment.load(in);
202.            in.close();
203.  
204.            if (comment != null) {
205.                this.captureSubmissionDetails(request, comment);
206.                result = CommentManager.INSTANCE.saveComment(comment, true);
207.            } else {
208.                builder.status(Status.NOT_ACCEPTABLE);
209.            }
210.            builder.entity(result).type(MediaType.TEXT_HTML_TYPE);
211.  
212.        } catch (Exception e) {
213.            String errorMessage = e.getMessage();
214.            builder.entity((((errorMessage == null) || errorMessage.equals("")) ? "Undefined error" : errorMessage)).type(
215.                    MediaType.TEXT_HTML_TYPE);
216.            Utils.logError(this.logger, e);
217.        }
218.  
219.        mon.stop();
220.        return builder.build();
221.    }
222.  
223.    @GET
224.    public Response getComments(@QueryParam("parentid") final String parentid) {
225.        Response response = null;
226.        final Monitor mon = MonitorFactory.start("CommentService#getComments");
227.        final ResponseBuilder builder = Response.ok();
228.        final Collection<BlogComment> bc = CommentManager.INSTANCE.loadComments(parentid);
229.  
230.        if ((bc == null) || bc.isEmpty()) {
231.            builder.status(Status.NO_CONTENT);
232.        } else {
233.            response = this.renderOutput(bc, "comment.mustache");
234.        }
235.        mon.stop();
236.        return (response == null) ? builder.build() : response;
237.    }
238.  
239.    private void captureSubmissionDetails(HttpServletRequest request, BlogComment comment) {
240.        final Monitor mon = MonitorFactory.start("CommentService#captureSubmissionDetails");
241.        try {
242.            @SuppressWarnings("rawtypes")
243.            Enumeration hn = request.getHeaderNames();
244.            if (hn != null) {
245.                while (hn.hasMoreElements()) {
246.                    String key = hn.nextElement().toString();
247.                    comment.addParameter(key, request.getHeader(key));
248.                }
249.            }
250.            @SuppressWarnings("rawtypes")
251.            Enumeration pn = request.getParameterNames();
252.            if (pn != null) {
253.                while (pn.hasMoreElements()) {
254.                    String key = pn.nextElement().toString();
255.                    String[] values = request.getParameterValues(key);
256.                    comment.addParameters(key, values);
257.  
258.                    if (key.equals("referer")) {
259.                        comment.setReferer(values[0]);
260.                    } else if (key.equals("user-agent")) {
261.                        comment.setUserAgent(values[0]);
262.                    }
263.  
264.                }
265.            }
266.            @SuppressWarnings("rawtypes")
267.            Enumeration an = request.getAttributeNames();
268.            if (an != null) {
269.                while (an.hasMoreElements()) {
270.                    try {
271.                        String key = an.nextElement().toString();
272.                        comment.addAttribute(key, String.valueOf(request.getAttribute(key)));
273.                    } catch (Exception e) {
274.                        // No action here
275.                    }
276.                }
277.            }
278.            comment.addParameter("REMOTE_HOST", request.getRemoteHost());
279.            comment.addParameter("REMOTE_ADDR", request.getRemoteAddr());
280.            comment.addParameter("REMOTE_USER", request.getRemoteUser());
281.  
282.            // Needed for Captcha
283.            comment.setRemoteAddress(request.getRemoteAddr());
284.        } catch (Exception e) {
285.            Utils.logError(this.logger, e);
286.            // But no further action here!
287.        }
288.        mon.stop();
289.    }
290. }
291. &lt;/pre&gt;</description>
292. <link>2017/05/from-blogsphere-to-a-static-site-part-4-comment-backend.html</link>
293. <author>Stephan H Wissel</author>
294. <guid>5CD6877EE6BFF61948258116003F5BF6</guid>
295. <pubDate>2017-05-04 07:32</pubDate>
296.  
297. </item>
298. <item><title>The Decline and Fall of IBM</title>
299. <description>&lt;p&gt;I wrote this quite a while ago, never finished the article until now. Enjoy. &lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
300. <p><b>Yeah right!</b></p>
301. <p>With this words <a href="http://www.cringely.com/">Robert X Cringley</a> a.k.a Mark Stephens celebrates himself when he asserts something clever. His book <a href="http://amzn.to/2qnDi7j">The Decline and Fall of IBM</a> created quite some stir and was a hot topic of discussion especially among IBMers and alumni.<br /> So I got myself a copy and had a look. Clearly he has an axe to grind with IBM and everybody is invited. Many came. Half of the book consists of mostly grieving comments ranging from 2007 until 2014. With all this contributions, the content remains light on substance. After all it costs you less than a late.</p>
302. <p>Some of the stated observations are spot on, like "<i>IBM is a sales organisation</i>", others while looking like observations, but rather are opinions (e.g. "<i>IBM lost its way</i>") and statements that made me feel: "<i>why didn't the IBM board ask him to run IBM? He seems to know so much better!</i>", exactly like an arbitrary spectator of the world cup in a pub can tell you what a team did wrong.</p>
303. <p>I'm not saying, that all is well in IBM, that would be <a href="https://www.fool.com/quote/nyse/ibm/ibm" title="They don't share that view either">a fools view</a>. An organisation with a size and workforce exceeding several countries does live in challenging times. An economic system, that values growth over everything is problematic (In biology an organism that grows indefinitely is called cancer) at least and transiting to a global workforce on this scale is unparalleled. I share his view that the dance around the <a href="https://en.wikipedia.org/wiki/Golden_calf">golden calf</a> known as <a href="https://www.forbes.com/sites/stevedenning/2011/11/28/maximizing-shareholder-value-the-dumbest-idea-in-the-world/">shareholder value</a> might be praying to a false good.<br />Here are some comments to Cringley's statements, that crossed my mind (paraphrasing):</p>
304. <ul>
305. <li>Cringley: <i>"In IBM management is royalty, the sales force the nobility and technical people are the peasants. No peasant can dream to become royalty"</i>.<br /> <b>Yeah right!</b> IBM fellows, IBM Distinguished Engineers or members of the IBM Academy of Technology will disagree. The irony here: in the "good old IBM (of Watson)" there was no career path for technical experts. In the IBM of today there is</li>
306. <li>I worked a lot with our engineers in India and China. They are hard working, ready to learn and, by now, quite experienced. Asserting that they are less capable that their American counterparts, seems quite arrogant to me. Yes, they were unexperienced a decade ago, but that's a long time in IT years. Also: there are capable and incapable engineers everywhere. Pinning it on a specific country or region is (insert your own statement of backwards here). A real issue however are IBM's processes, that had been designed to cater to get less experienced people on board. They need an overhaul.</li>
307. <li>Cringley: <i>"IBM should not sell the Intel servers to Lenovo"</i>.<br /> <b>Yeah right!</b> Cringley portrays it as the complete exit out of a server growth market. However IBM still has Intel based technology in their PureSystems and acquired skills and know how through the Softlayer acquisition how to build the special segment of Intel based machines that run in cloud size data centres. So instead of exiting a segment, it looks to me like eliminating duplicate product lines</li>
308. <li>Cringley: <i>"IBM should port AIX to Intel"</i>.<br /> <b>Yeah right!</b> AIX runs on one class of IBM machines (System P), while Linux runs on everything from
309.  <strike>
310.    Softlayer
311.  </strike>Bluemix to Mainframe. Linux outperforms AIX on System P in quite some workloads. So what makes a better investment? Port AIX or infuse the security know how of AIX into Linux? (the file system options are there already)</li>
312. <li>Cringley: <i>"IBM should ditch the Power architecture and switch to Intel"</i><br /> <b>Yeah right!</b> IBM has vast know how in building processors that will get lost when stopping to develop them. Asset utilisation isn't ditching assets, but making them more competitive. Intel and ARM aren't the only shops who can design processors, just have a look at <a href="http://openpowerfoundation.org/">OpenPOWER</a></li>
313. <li>Cringley: <i>Hadoop will make mainframes obsolete</i>.<br /> <b>Yeah right!</b> The technology is around for a decade, Google, its inventor, already moved on. Asserting a single technology will kill the I/O beasts known as Big Iron, looks like an inflight magazine statement. Besides the fact, that IBM offers a robust Hadoop implementation for a while already, which you can run on zLinux, if you choose so.</li>
314. <li>The book contains quite some areas, like current staff morale, the process culture or the layers of management that highlight pain. However where he is wrong: IBM isn't blind to the issues and there are forces inside working for the betterment (even if there is a case of a <a href="http://amzn.to/2pwgjab">Knowing-Doing-Gap</a>)</li>
315. </ul> Of course, YMMY, so
316. &lt;a href="http://amzn.to/2qnDi7j"&gt;read it for yourself&lt;/a&gt;</description>
317. <link>2017/05/the-decline-and-fall-of-ibm.html</link>
318. <author>Stephan H Wissel</author>
319. <guid>FAD76A0F746D9A3748257D04003A257E</guid>
320. <pubDate>2017-05-01 12:35</pubDate>
321.  
322. </item>
323. <item><title>From Blogsphere to a Static Site (Part 3) - Generating pages</title>
324. <description>&lt;p&gt;The rendering engine I choose is &lt;a href="mustache.github.com/mustache.5.html"&gt;mustache&lt;/a&gt; which describes itself as &amp;quot;&lt;i&gt;logic-less templating engine&lt;/i&gt;&amp;quot;. My main criteria was the availability on multiple platforms including &lt;a href="https://github.com/spullara/mustache.java"&gt;Java&lt;/a&gt; and &lt;a href="https://github.com/janl/mustache.js"&gt;JavaScript&lt;/a&gt; (I might port the rendering part to NodeJS at some time in the future).&lt;br /&gt; The only logic mustache supports is conditional rendering based on the presence or absence of an element. When an element is present and is an array (or a collection in Java) the body of the template gets repeated for each element in the array. A scalar value hence is treated as an array with one value only.&lt;/p&gt;
325. <p>Mustache is simple to use. All you need is a data bean (in Java, a JSON structure for JavaScript) and a text file containing placeholders with the property names. E.g. <code><h1>{{title}}</h1></code> will render a headline with the title property of you data object. In Java that would be either a public variable or a call to <code>getTitle</code> according to the bean specification. The blog rendering code therefore is quite simple:</p>
326. <pre class="brush: java">
327. private void renderOneEntry(BlogEntry be, Mustache mustache) throws IOException {
328.  
329.        String location = this.config.destinationDirectory + be.getNewURL();
330.        String outDirs = location.substring(0, location.lastIndexOf("/"));
331.        File dirs = new File(outDirs);
332.        if (!dirs.exists()) {
333.            dirs.mkdirs();
334.        }
335.        // Set the current context
336.        for (LinkItem cat : be.getCategory()) {
337.            String c = cat.name;
338.            this.allCategories.get(c.toLowerCase()).active = true;
339.        }
340.        this.allDateCategories.get(be.getDateYear()).active = true;
341.  
342.        if (be.getSeries() != null) {
343.            String series = be.getSeries();
344.            if (this.allSeries.containsKey(series)) {
345.                this.allSeries.get(series).get(be.getNewURL()).active = true;
346.            }
347.        }
348.  
349.        // Prepare to write out
350.        ByteArrayOutputStream out = new ByteArrayOutputStream(102400);
351.        Writer pw = new PrintWriter(out);
352.  
353.        // This is where the magic happens
354.        mustache.execute(pw, be);
355.        pw.flush();
356.        pw.close();
357.        this.saveIfChanged(out.toByteArray(), location);
358.  
359.        // Cleanup
360.        for (LinkItem cat : be.getCategory()) {
361.            String c = cat.name;
362.            this.allCategories.get(c.toLowerCase()).active = false;
363.        }
364.        this.allDateCategories.get(be.getDateYear()).active = false;
365.  
366.        if (be.getSeries() != null) {
367.            String series = be.getSeries();
368.            if (this.allSeries.containsKey(series)) {
369.                this.allSeries.get(series).get(be.getNewURL()).active = false;
370.            }
371.        }
372.    }
373. </pre>
374. &lt;p&gt;The actual rendering is just the line &lt;code&gt;mustache.execute(pw, be);&lt;/code&gt; The code around it prepares and resets the collections that might render on a page like categories, series or month and year. Also of interest is &lt;code&gt;this.saveIfChanged(out.toByteArray(), location);&lt;/code&gt; which only saves results back to disk if it actually has changed. Don't be mistaken: any change in layout will lead to a newly rendered page, so this is quite important to save as needed and not more (you don't want to have tons of identical files that only differ in their time stamp)&lt;/p&gt;</description>
375. <link>2017/05/from-blogsphere-to-a-static-site-part-3-generating-pages.html</link>
376. <author>Stephan H Wissel</author>
377. <guid>02FE470F4B650113482581130012A956</guid>
378. <pubDate>2017-05-01 11:23</pubDate>
379.  
380. </item>
381. <item><title>From Blogsphere to a Static Site (Part 2) - Cleaning up the HTML</title>
382. <description>&lt;p&gt;Blogsphere allows to create RichText and plain HTML entries. To export them I need to grab the HTML, either the manual entered or the RichText generated on, clean it up (especially for my manual entered HTML) and then replace image sources and internal links using the new URL syntax. To make this happen I created 2 functions that saved images and attachments and created a lookup list, so the HTML cleanup has a mapping table to work with&lt;/p&gt;
383. <pre class="brush: java">
384. private void saveImage(Document doc) {
385.        String sourceDirectory = this.config.sourceDirectory + this.config.imageDirectory;
386.        try {
387.            String subject = doc.getItemValueString("ImageName");
388.            Date created = doc.getCreated().toJavaDate();
389.            @SuppressWarnings("rawtypes")
390.            Vector attNames = this.s.evaluate("@AttachmentNames", doc);
391.            String description = doc.getItemValueString("ImageName");
392.            String oldURL = this.config.oldImageLocation + doc.getItemValueString("ImageUNID") + "/$File/";
393.            SimpleDateFormat sdf = new SimpleDateFormat("yyyy");
394.            String year = sdf.format(created);
395.            FileEntry fe = this.imgEntries.add(subject, oldURL, description, created);
396.  
397.            for (Object attObj : attNames) {
398.                try {
399.                    String attName = attObj.toString();
400.                    String newURL = this.config.webBlogLocation + this.config.imageDirectory + year + "/" + attName;
401.                    fe.add(attName, newURL, description, created);
402.                    String outDir = sourceDirectory + year + "/";
403.                    this.ensureDirectory(outDir);
404.                    EmbeddedObject att = doc.getAttachment(attName);
405.                    att.extractFile(outDir + attName);
406.                    Utils.shred(att);
407.                } catch (NotesException e) {
408.                    e.printStackTrace();
409.                } catch (Exception e2) {
410.                    e2.printStackTrace();
411.                }
412.            }
413.  
414.        } catch (NotesException e) {
415.            e.printStackTrace();
416.        }
417.  
418.    }
419.  
420.    private void saveImageFromURL(String href, String targetName) {
421.  
422.        String fetchFromWhere = "https://" + this.config.bloghost + href;
423.        try {
424.            byte[] curImg = Request.Get(fetchFromWhere).execute().returnContent().asBytes();
425.            this.saveIfChanged(curImg, targetName);
426.        } catch (ClientProtocolException e) {
427.            e.printStackTrace();
428.        } catch (IOException e) {
429.            e.printStackTrace();
430.        }
431.  
432.    }
433. </pre>
434. &lt;p&gt;With images saved the HTML cleanup can proceed. As mentioned before I'm using &lt;a href="https://jsoup.org/"&gt;JSoup&lt;/a&gt; to process crappy HTML. It allows for easy extraction of elements and attributes, so processing of links an images is just a few lines&lt;/p&gt;</description>
435. <link>2017/04/from-blogsphere-to-a-static-site-part-2-cleaning-up-the-html.html</link>
436. <author>Stephan H Wissel</author>
437. <guid>922F997388C85F0548258105004A17A1</guid>
438. <pubDate>2017-04-17 09:29</pubDate>
439.  
440. </item>
441.  
442. </channel>
443. </rss>
444.  

Home · About · News · Docs · Terms