<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software Engineering on code.kiwi.com</title><link>https://code.kiwi.com/tag/software-engineering/</link><description>Recent content in Software Engineering on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Mar 2023 21:03:39 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/software-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>The Career Framework 2 years later: How it impacts our engineering culture at Kiwi.com</title><link>https://code.kiwi.com/articles/the-career-framework-2-years-later-how-it-impacts-our-engineering-culture-at-kiwi-com/</link><pubDate>Wed, 09 Mar 2022 20:05:00 +0000</pubDate><guid>https://code.kiwi.com/articles/the-career-framework-2-years-later-how-it-impacts-our-engineering-culture-at-kiwi-com/</guid><description>&lt;p&gt;Two years ago, if you asked what you should do to get promoted, every team lead at Kiwi.com would give you a different answer (or just a shoulder shrug). And there are more questions you could ask: How do I grow my career? Am I performing well? What is the next step for me? Am I compensated fairly? Even in the context of other teams and departments?&lt;/p&gt;</description></item><item><title>5 Reasons to Write a Document Before Writing Code</title><link>https://code.kiwi.com/articles/5-reasons-to-write-a-document-before-writing-code/</link><pubDate>Wed, 22 Apr 2020 18:39:00 +0000</pubDate><guid>https://code.kiwi.com/articles/5-reasons-to-write-a-document-before-writing-code/</guid><description>&lt;p&gt;Writing a proper design document is often frowned upon. Whether it is an RFC or a problem specification — it doesn’t matter what you call it — the usual reaction is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Ain’t nobody got time for that. We need to write code.&lt;/p&gt;</description></item></channel></rss>