<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>PyVideo.org - Fredrik Håård</title><link href="https://pyvideo.org/" rel="alternate"></link><link href="https://pyvideo.org/feeds/speaker_fredrik-haard.atom.xml" rel="self"></link><id>https://pyvideo.org/</id><updated>2014-07-24T00:00:00+00:00</updated><subtitle></subtitle><entry><title>Minimalism in software development, or why you should do less</title><link href="https://pyvideo.org/europython-2012/minimalism-in-software-development-or-why-you-sh.html" rel="alternate"></link><published>2012-07-06T00:00:00+00:00</published><updated>2012-07-06T00:00:00+00:00</updated><author><name>Fredrik Haard</name></author><id>tag:pyvideo.org,2012-07-06:/europython-2012/minimalism-in-software-development-or-why-you-sh.html</id><summary type="html">&lt;h3&gt;Summary&lt;/h3&gt;&lt;p&gt;[EuroPython 2012] Fredrik Haard - 5 JULY 2012 in &amp;quot;Track Lasagne&amp;quot;&lt;/p&gt;
&lt;h3&gt;Description&lt;/h3&gt;&lt;p&gt;Lean and agile promises - when implemented right - to reduce the pain of
process and management overhead. As agile proponents say (the better of
them at least), this does not actually solve all our problems, it merely
lets us …&lt;/p&gt;</summary><content type="html">&lt;h3&gt;Summary&lt;/h3&gt;&lt;p&gt;[EuroPython 2012] Fredrik Haard - 5 JULY 2012 in &amp;quot;Track Lasagne&amp;quot;&lt;/p&gt;
&lt;h3&gt;Description&lt;/h3&gt;&lt;p&gt;Lean and agile promises - when implemented right - to reduce the pain of
process and management overhead. As agile proponents say (the better of
them at least), this does not actually solve all our problems, it merely
lets us see them clearer. And one thing that we can see clear once
management overhead goes down, is that we are perfectly able to create
our own, technical, overhead. Developer culture and a tendency of
solving problems ‘the usual way’ can - and does - create complicated
solutions to simple problems, and regularly leaves us in configuration
hell. This is a talk about frameworks and API:s, programming languages
and data storage, and why we - developers - spend a large amount of time
not creating value. Even if we have the most perfect of agile
implementations with zero process overhead (yeah, right!), we still
waste time in development, and its all our own fault. I will discuss
what we spend our time on, why any framework should be approached with
trepidation, and how we can do better than keep repeating the mistakes
of yesteryear.&lt;/p&gt;
</content><category term="EuroPython 2012"></category></entry><entry><title>User to framework author in four hours - Part 1</title><link href="https://pyvideo.org/europython-2013/user-to-framework-author-in-four-hours-part-1.html" rel="alternate"></link><published>2013-07-03T00:00:00+00:00</published><updated>2013-07-03T00:00:00+00:00</updated><author><name>Fredrik Håård</name></author><id>tag:pyvideo.org,2013-07-03:/europython-2013/user-to-framework-author-in-four-hours-part-1.html</id><content type="html"></content><category term="EuroPython 2013"></category><category term="best-practices"></category><category term="framework"></category><category term="python3"></category><category term="interactive"></category></entry><entry><title>User to framework author in four hours - Part 2</title><link href="https://pyvideo.org/europython-2013/user-to-framework-author-in-four-hours-part-2.html" rel="alternate"></link><published>2013-07-03T00:00:00+00:00</published><updated>2013-07-03T00:00:00+00:00</updated><author><name>Fredrik Håård</name></author><id>tag:pyvideo.org,2013-07-03:/europython-2013/user-to-framework-author-in-four-hours-part-2.html</id><content type="html"></content><category term="EuroPython 2013"></category><category term="best-practices"></category><category term="framework"></category><category term="python3"></category><category term="interactive"></category></entry><entry><title>Jython in practice</title><link href="https://pyvideo.org/europython-2014/jython-in-practice.html" rel="alternate"></link><published>2014-07-24T00:00:00+00:00</published><updated>2014-07-24T00:00:00+00:00</updated><author><name>Fredrik Håård</name></author><id>tag:pyvideo.org,2014-07-24:/europython-2014/jython-in-practice.html</id><summary type="html">&lt;h3&gt;Summary&lt;/h3&gt;&lt;p&gt;A lot of people have heard of Jython, some have tried it, but it seems
few have actually deployed it in a corporate environment. In this talk
I'll share my experiences in using Jython as a testbed for Java
applications, for rapid prototyping in Java desktop and web
environments …&lt;/p&gt;</summary><content type="html">&lt;h3&gt;Summary&lt;/h3&gt;&lt;p&gt;A lot of people have heard of Jython, some have tried it, but it seems
few have actually deployed it in a corporate environment. In this talk
I'll share my experiences in using Jython as a testbed for Java
applications, for rapid prototyping in Java desktop and web
environments, and for embedding scripting capabilities in Java products.&lt;/p&gt;
&lt;h3&gt;Description&lt;/h3&gt;&lt;p&gt;Not everyone gets paid to work with Python all the time, but if you find
yourself in a Java project, there are good chances you could benefit
from Python without throwing out the Java stack. Using Jython, you can
do rapid prototyping without the long edit-compile-test cycles normally
associated with large Java projects, whether on the web or the desktop,
and when testing an application might become a nightmare of scaffolding
in Java, a little Jython may be just what you need to be able to run
your tests smoothly.&lt;/p&gt;
&lt;p&gt;At the end of this talk, I will put on my politician´s hat and bring up
the best - and worst - arguments to use to get permission to use Jython
in a corporate environment.&lt;/p&gt;
</content><category term="EuroPython 2014"></category></entry></feed>