<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Big-O on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/big-o/</link><description>Recent content in Big-O on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Thu, 13 Jul 2023 20:54:08 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/big-o/index.xml" rel="self" type="application/rss+xml"/><item><title>Binary Search – Algorithm and Time Complexity Explained</title><link>http://karpoke.ignaciocano.com/2023/07/13/binary-search-algorithm-and-time-complexity-explained/</link><pubDate>Thu, 13 Jul 2023 20:54:08 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2023/07/13/binary-search-algorithm-and-time-complexity-explained/</guid><description>&lt;blockquote&gt;
&lt;p&gt;When working with arrays, you’ll often have to search through them to
check if they contain a target element. You can always run a sequential
search—scanning the array from the beginning to the end—on the array.
But if the array is sorted, running th&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» freeCodeCamp.org | &lt;a href="https://www.freecodecamp.org/news/binary-search-algorithm-and-time-complexity-explained/"&gt;freecodecamp.org&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Big O Cheat Sheet – Time Complexity Chart</title><link>http://karpoke.ignaciocano.com/2022/10/07/big-o-cheat-sheet-time-complexity-chart/</link><pubDate>Fri, 07 Oct 2022 11:00:30 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2022/10/07/big-o-cheat-sheet-time-complexity-chart/</guid><description>&lt;blockquote&gt;
&lt;p&gt;An algorithm is a set of well-defined instructions for solving a
specific problem. You can solve these problems in various ways. This
means that the method you use to arrive at the same solution may differ
from mine, but we should both get the same r&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» olawanletjoel | &lt;a href="https://www.freecodecamp.org/news/big-o-cheat-sheet-time-complexity-chart/"&gt;freecodecamp.org&lt;/a&gt;&lt;/p&gt;</description></item><item><title>The Big O</title><link>http://karpoke.ignaciocano.com/2022/08/03/the-big-o/</link><pubDate>Wed, 03 Aug 2022 16:58:53 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2022/08/03/the-big-o/</guid><description>&lt;blockquote&gt;
&lt;p&gt;The Big O is a way to measure how well your code solves a problem&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/the-big-o"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Big O, code efficiency analysis</title><link>http://karpoke.ignaciocano.com/2021/08/13/big-o-code-efficiency-analysis/</link><pubDate>Fri, 13 Aug 2021 14:13:01 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/08/13/big-o-code-efficiency-analysis/</guid><description>&lt;blockquote&gt;
&lt;p&gt;In this article I would do my best to introduce you to algorithmic
complexity and a way to roughly&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/kerosz/big-o-code-efficiency-analysis-phk"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Four Rules for Big O</title><link>http://karpoke.ignaciocano.com/2021/07/26/four-rules-for-big-o/</link><pubDate>Mon, 26 Jul 2021 07:56:57 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/07/26/four-rules-for-big-o/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Worst case When calculating for the Big O of algorithms we’re supposed
to assume the&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/coderjay06/four-rules-for-big-o-1915"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Big(O) Notation summarized!</title><link>http://karpoke.ignaciocano.com/2021/07/09/big-o-notation-summarized/</link><pubDate>Fri, 09 Jul 2021 14:32:09 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/07/09/big-o-notation-summarized/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Big(O) is the way in which we compare algorithmic complexities of two
programs in a standard&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/chinedu/big-o-notaion-summarized-1fb8"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Big O Notation</title><link>http://karpoke.ignaciocano.com/2021/01/13/big-o-notation/</link><pubDate>Wed, 13 Jan 2021 09:01:13 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2021/01/13/big-o-notation/</guid><description>&lt;blockquote&gt;
&lt;p&gt;-Intro to Big O -Timing Our Code -Counting&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/code_regina/big-o-notation-2ng0"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>A Gentle Introduction to the Big O Notation, Time &amp; Space Complexity</title><link>http://karpoke.ignaciocano.com/2020/10/15/a-gentle-introduction-to-the-big-o-notation-time-space-complexity/</link><pubDate>Thu, 15 Oct 2020 14:50:52 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/10/15/a-gentle-introduction-to-the-big-o-notation-time-space-complexity/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Introduction I have been in Software Engineering for a decade and a half
and I am not a Co&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/skaytech/a-gentle-introduction-to-the-big-o-notation-time-space-complexity-3hdd"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Big O Notation for beginners!!</title><link>http://karpoke.ignaciocano.com/2020/08/15/big-o-notation-for-beginners/</link><pubDate>Sat, 15 Aug 2020 17:23:56 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/08/15/big-o-notation-for-beginners/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Why beginners should not be afraid of AL As a code newbie, I have read a
few posts that sa&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/tracycss/big-o-notation-for-beginners-4b51"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Big-O For the Non-CS Degree - Part 2</title><link>http://karpoke.ignaciocano.com/2020/07/04/big-o-for-the-non-cs-degree-part-2/</link><pubDate>Sat, 04 Jul 2020 20:27:14 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/07/04/big-o-for-the-non-cs-degree-part-2/</guid><description>&lt;blockquote&gt;
&lt;p&gt;If you’re reading this, and haven’t read part one in the series I
recommend reading that first. There&amp;hellip;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/travislramos/big-o-for-the-non-cs-degree-part-2-11cc"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Notes on algorithms</title><link>http://karpoke.ignaciocano.com/2020/01/10/notes-on-algorithms/</link><pubDate>Fri, 10 Jan 2020 23:25:21 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2020/01/10/notes-on-algorithms/</guid><description>&lt;blockquote&gt;
&lt;p&gt;notes on algorithms after CS50 week 3&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» DEV Community | &lt;a href="https://dev.to/hexangel616/notes-on-algorithms-36pi"&gt;dev.to&lt;/a&gt;&lt;/p&gt;</description></item><item><title>A Gentle Introduction to Algorithm Complexity Analysis</title><link>http://karpoke.ignaciocano.com/2012/07/05/a-gentle-introduction-to-algorithm-complexity-analysis/</link><pubDate>Thu, 05 Jul 2012 18:17:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/07/05/a-gentle-introduction-to-algorithm-complexity-analysis/</guid><description>&lt;blockquote&gt;
&lt;p&gt;A lot of programmers that make some of the coolest and most useful
software today, such as many of the stuff we see on the Internet or
use daily, don’t have a theoretical computer science background.
They’re still pretty awesome and creative programmers and we thank
them for what they build.&lt;/p&gt;
&lt;p&gt;However, theoretical computer science has its uses and applications
and can turn out to be quite practical. In this article, targeted at
programmers who know their art but who don’t have any theoretical
computer science background, I will present one of the most pragmatic
tools of computer science: Big O notation and algorithm complexity
analysis. As someone who has worked both in a computer science
academic setting and in building production-level software in the
industry, this is the tool I have found to be one of the truly useful
ones in practice, so I hope after reading this article you can apply
it in your own code to make it better. After reading this post, you
should be able to understand all the common terms computer scientists
use such as ”big O”, ”asymptotic behavior” and ”worst-case analysis”.&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>