<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sebastian Vargr</title>
    <description>The latest articles on DEV Community by Sebastian Vargr (@sebbdk).</description>
    <link>https://dev.to/sebbdk</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F162707%2Fec9d10df-acbb-4827-816e-6e4706275a32.png</url>
      <title>DEV Community: Sebastian Vargr</title>
      <link>https://dev.to/sebbdk</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sebbdk"/>
    <language>en</language>
    <item>
      <title>Aha! I discovered Conway's law</title>
      <dc:creator>Sebastian Vargr</dc:creator>
      <pubDate>Wed, 21 Oct 2020 11:47:55 +0000</pubDate>
      <link>https://dev.to/sebbdk/aha-i-discovered-conway-s-law-2h02</link>
      <guid>https://dev.to/sebbdk/aha-i-discovered-conway-s-law-2h02</guid>
      <description>&lt;p&gt;&lt;strong&gt;Intro&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;A friend of mine introduced me to the concept of Conway's law, and it triggered a classic aha! moment for me, so now I am looking for more opinions to challenge my psyched bias.&lt;/p&gt;

&lt;p&gt;So let's share experiences. :)&lt;/p&gt;

&lt;p&gt;If you do not know Conway's law, here is the gist of it grabbed from &lt;a href="https://en.wikipedia.org/wiki/Conway%27s_law"&gt;Wikipedia&lt;/a&gt;.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Conway's law is an adage stating that organizations design systems that mirror their own communication structure.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;p&gt;&lt;strong&gt;Story&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I've been learning to be a team/tech lead the past year and I have struggled with it since at my core I am a web application architect, I solve code problems, not organization problems.&lt;/p&gt;

&lt;p&gt;I feel Conway's law is a really good new perspective for me.&lt;br&gt;
Not to blame' everyone else, but as a tool to recognize when communication breaks down and how it reflects on the code/architecture.&lt;/p&gt;

&lt;p&gt;Fx. some features got implemented really badly, how did that come about? What part of the decision making failed.&lt;/p&gt;

&lt;p&gt;It's easy to blame developers for fx. not testing enough, but I find often bad code happens when developers are not working the same way, have decent specs, or when they are working too many domains at once.&lt;/p&gt;

&lt;p&gt;I've been fretting about teaching my colleagues/juniors how to use the tools we have efficiently, but maybe what I should have been doing is limiting the domain that we work with to make sure we get good at one thing at a time.&lt;/p&gt;

&lt;p&gt;This is definitely something I will try and apply in the future as well as looking at previous problems through this lens.&lt;/p&gt;




&lt;p&gt;What are your thoughts on Conway's law?&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What are your experiences with Conway's law?&lt;/li&gt;
&lt;li&gt;How have you used it, or seen it applied?&lt;/li&gt;
&lt;li&gt;And do you have any advice on how to apply it from a team/tech lead perspective?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;let's discuss it! :)&lt;/p&gt;

&lt;p&gt;Keep your eye on the birdie!&lt;br&gt;
Vargr&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>conway</category>
      <category>management</category>
      <category>teamlead</category>
    </item>
    <item>
      <title>"I'll be emailing you weekly" - Yeah, no, stop.</title>
      <dc:creator>Sebastian Vargr</dc:creator>
      <pubDate>Fri, 10 Jul 2020 20:50:20 +0000</pubDate>
      <link>https://dev.to/sebbdk/i-ll-be-emailing-you-weekly-yeah-no-stop-3076</link>
      <guid>https://dev.to/sebbdk/i-ll-be-emailing-you-weekly-yeah-no-stop-3076</guid>
      <description>&lt;p&gt;I got this e-mail title "I'll be emailing you weekly" today from dev.to,&lt;/p&gt;

&lt;p&gt;This actually hit a nerve.&lt;/p&gt;

&lt;p&gt;No you do not get to email me another weekly without me asking.&lt;br&gt;
This email prompted me to disable the weekly's...&lt;/p&gt;

&lt;p&gt;Anyone else got annoyed by this?&lt;/p&gt;

&lt;p&gt;Also, and this might be subjective, but i feel like the amount of email CTA's have been increasing during my year on the site, anyone else noticed this?&lt;/p&gt;

&lt;p&gt;I hope this finds the right audience.&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>email</category>
      <category>marketing</category>
      <category>spam</category>
    </item>
    <item>
      <title>Coding to relax from obligations</title>
      <dc:creator>Sebastian Vargr</dc:creator>
      <pubDate>Wed, 27 May 2020 14:50:25 +0000</pubDate>
      <link>https://dev.to/sebbdk/coding-to-relax-from-obligations-2b98</link>
      <guid>https://dev.to/sebbdk/coding-to-relax-from-obligations-2b98</guid>
      <description>&lt;p&gt;Going through a stressfull period at work at the moment.&lt;br&gt;
Finally got a chance to code without interruptions this afternoon.&lt;/p&gt;

&lt;p&gt;It was pure bliss, just me, the problems in front me, and the ecstatic feeling of flow.&lt;/p&gt;

&lt;p&gt;I am considering asking my manager to have a "vacation" from my team/teck lead role to rest up a bit, might even be a good opportunity for me to train a standin for when i am on vacation etc.&lt;/p&gt;

&lt;p&gt;Anyone else have similar experiences? &lt;/p&gt;

</description>
      <category>teamlead</category>
      <category>techlead</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Ignoring performance</title>
      <dc:creator>Sebastian Vargr</dc:creator>
      <pubDate>Sun, 08 Mar 2020 18:26:46 +0000</pubDate>
      <link>https://dev.to/sebbdk/ignoring-performance-24eo</link>
      <guid>https://dev.to/sebbdk/ignoring-performance-24eo</guid>
      <description>&lt;p&gt;I see a pattern where developers ignore performance if it is not seen as an eminent problem.&lt;/p&gt;

&lt;p&gt;Examples of this could be ignoring components re-rendering excessively because it's not a real performance problem yet for the targets user,  accepting that derived state is calculated unnecessary, having cookies/headers on requests that have no need for them etc.&lt;/p&gt;

&lt;p&gt;From a business perspective this makes good sense.&lt;br&gt;
There are usually better business gains elsewhere.&lt;/p&gt;

&lt;p&gt;I also do this myself at work.&lt;/p&gt;

&lt;p&gt;But 10+ browser tabs with these kinda of shenanigans going in them + other applications add up.&lt;/p&gt;

&lt;p&gt;Especially when we start to consider mobile devices.&lt;/p&gt;

&lt;p&gt;That leaves me wondering..&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Isn't this kinda of lying to our selves by only looking at best case scenarios? &lt;/li&gt;
&lt;li&gt;When does this become too puristic?&lt;/li&gt;
&lt;li&gt;How could we mitigate this in a way that makes sense business wise?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Edit, extra question.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How would we measure if this is a problem for users in a none-intrusive way?&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>discuss</category>
      <category>performance</category>
    </item>
    <item>
      <title>Git jokes, giv em here!</title>
      <dc:creator>Sebastian Vargr</dc:creator>
      <pubDate>Fri, 03 Jan 2020 21:27:22 +0000</pubDate>
      <link>https://dev.to/sebbdk/git-jokes-giv-em-here-5271</link>
      <guid>https://dev.to/sebbdk/git-jokes-giv-em-here-5271</guid>
      <description>&lt;p&gt;It occurred to me that there is good material in git for jokes.&lt;/p&gt;

&lt;p&gt;So I’ve decided to git good and commit to pushing this thread until it becomes the base for my repository of bad puns.&lt;/p&gt;

&lt;p&gt;So share with me your stash of unstaged jokes will you? &lt;/p&gt;

&lt;p&gt;I promise I won’t be cherry-picky!&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>jokes</category>
      <category>git</category>
    </item>
  </channel>
</rss>
