<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Faiz Miftakhur on Medium]]></title>
        <description><![CDATA[Stories by Faiz Miftakhur on Medium]]></description>
        <link>https://medium.com/@fmrozaqi?source=rss-b8db7ae6c5e9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mI5CXGfZZMYbZads</url>
            <title>Stories by Faiz Miftakhur on Medium</title>
            <link>https://medium.com/@fmrozaqi?source=rss-b8db7ae6c5e9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 17:24:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@fmrozaqi/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[WSL Crashing Wsl/Service/HCS_E_CONNECTION_TIMEOUT]]></title>
            <link>https://fmrozaqi.medium.com/wsl-crashing-wsl-service-hcs-e-connection-timeout-e6a76a68fd99?source=rss-b8db7ae6c5e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6a76a68fd99</guid>
            <category><![CDATA[wsl]]></category>
            <category><![CDATA[wsl-2]]></category>
            <dc:creator><![CDATA[Faiz Miftakhur]]></dc:creator>
            <pubDate>Wed, 18 Jun 2025 06:51:51 GMT</pubDate>
            <atom:updated>2025-06-18T06:51:51.042Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P1DImgtSjQ-v1dUNuCKnGQ.avif" /></figure><p>Please, WSL. Stop making dumb updates. It happened multiple times.</p><pre>The operation timed out because a response was not received from the virtual machine or container.<br>Error code: Wsl/Service/HCS_E_CONNECTION_TIMEOUT</pre><p>Thanks for someone who&#39;s raising this issue on GitHub <a href="https://github.com/microsoft/WSL/issues/12991">https://github.com/microsoft/WSL/issues/12991</a></p><p>Just downgrade it, download from GH Microsoft WSL</p><p><a href="https://github.com/microsoft/WSL/releases">Releases · microsoft/WSL</a></p><p>For now (18/06/2025) I use 2.5.9.0 the downgrade to 2.5.7.0</p><p>ISSUE SOLVED!!!<br>Thanks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6a76a68fd99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setup SQA Locally]]></title>
            <link>https://fmrozaqi.medium.com/setup-sqa-locally-2f6b82e73001?source=rss-b8db7ae6c5e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f6b82e73001</guid>
            <category><![CDATA[sonarqube-setup]]></category>
            <category><![CDATA[sonarqube]]></category>
            <category><![CDATA[sqa]]></category>
            <dc:creator><![CDATA[Faiz Miftakhur]]></dc:creator>
            <pubDate>Tue, 18 Feb 2025 07:43:13 GMT</pubDate>
            <atom:updated>2025-02-18T07:43:13.189Z</atom:updated>
            <content:encoded><![CDATA[<p>Outlines:</p><ol><li>Install sonarqube (using docker)</li><li>Install sonnar-scanner</li><li>Setup project property</li><li>Run scanner</li></ol><h3>Install Sonarqube (Docker)</h3><p>Install <strong>sonarqube </strong>image</p><pre>docker pull sonarqube</pre><p>Run the image</p><pre>docker run -d - name sonarqube -p 9000:9000 sonarqube</pre><p>For better installation read: <a href="https://docs.sonarsource.com/sonarqube-server/10.7/setup-and-upgrade/install-the-server/installing-sonarqube-from-docker/#create-volumes">https://docs.sonarsource.com/sonarqube-server/10.7/setup-and-upgrade/install-the-server/installing-sonarqube-from-docker/#create-volumes</a></p><h3>Install Sonnar-Scanner</h3><h4>Linux installation:</h4><p>Download app</p><pre>wget https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-7.0.1.4817-linux-x64.zip</pre><p>Unzip file</p><pre>unzip sonar-scanner-cli-7.0.1.4817-linux-x64.zip</pre><p>Move file</p><pre>sudo mv sonar-scanner-7.0.1.4817-linux-x64 /opt/sonar-scanner</pre><p>Register to bash</p><pre>echo &#39;export PATH=$PATH:/opt/sonar-scanner/bin&#39; &gt;&gt; ~/.bashrc<br>source ~/.bashrc</pre><p>Check if the installation succeed</p><pre>sonar-scanner -v</pre><h3>Setup project property</h3><p>Open <a href="http://localhost:9000/">http://localhost:9000/</a></p><p>Login with admin:admin (for initial run)</p><p>Create a local project</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XXmYlLorV7ip62NQFIDyUg.png" /></figure><p>Fill the form (you can fill anything on branch input)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/0*VUeFfMmsdMyRmKig" /></figure><p>Use global setting (for general purpose)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tT8Pc8sTm3ByHqyE" /></figure><p>Select Locally</p><p>Generate a token and save the key</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/0*EM2s4zPYMx09E-0V" /></figure><p>Create myproject.properties file and add some configuration</p><pre>sonar.projectKey=dasijr-gllm-backend<br>sonar.projectName=dasijr-gllm-backend<br>sonar.host.url=http://localhost:9000<br><br>sonar.language=python<br>sonar.python.version=3.11<br><br>sonar.ws.timeout=1200<br><br>sonar.sources=dasijr_gllm_backend/<br>sonar.inclusions=<br>sonar.exclusions=build/**/*,example/**/*<br><br>sonar.tests=tests/<br><br>sonar.coverage.exclusions=dasijr_gllm_backend/app.py,dasijr_gllm_backend/api/**/*<br>sonar.python.coverage.reportPaths=build/reports/gdplabs-gen-ai.xml</pre><p>Note: You can customize this section by reading <a href="https://docs.sonarsource.com/sonarqube-server/10.4/analyzing-source-code/scanners/sonarscanner/">https://docs.sonarsource.com/sonarqube-server/10.4/analyzing-source-code/scanners/sonarscanner/</a></p><h3>Run Scanner</h3><p>Run the scanner</p><pre>sonar-scanner -Dproject.settings=./myproject.properties -Dsonar.token=[sqa-token]</pre><p>Example</p><pre>sonar-scanner -Dproject.settings=./myproject.properties -Dsonar.token=sqp_cbc0e177e3aea943516dba30a5d02349fcbe5b0c</pre><p>Example Result</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eWgwyV3M5Q0W6ijk" /></figure><p>For coverage, please run the generate coverage result</p><p>Example on python</p><pre>REPORT_PATH=build/reports<br>mkdir -p &quot;$REPORT_PATH&quot;<br>poetry run coverage run -m pytest tests - ignore=tests/integration/run_llm<br>poetry run coverage report -m -i - skip-empty<br>poetry run coverage xml -i -o &quot;$REPORT_PATH/gdplabs-gen-ai.xml&quot;</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f6b82e73001" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hydration Error NextJS]]></title>
            <link>https://fmrozaqi.medium.com/hydration-error-nextjs-e58ef934f13a?source=rss-b8db7ae6c5e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e58ef934f13a</guid>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Faiz Miftakhur]]></dc:creator>
            <pubDate>Mon, 30 Dec 2024 07:53:53 GMT</pubDate>
            <atom:updated>2024-12-30T07:53:53.461Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9WaVE9GDn23ty2GHMwVTQ.png" /></figure><p>I got an error warning on loading my nextJS project. It shows that</p><pre>A tree hydrated but some attributes of the server rendered HTML didn&#39;t match the client properties. This won&#39;t be patched up. This can happen if a SSR-ed Client Component used:<br>- A server/client branch `if (typeof window !== &#39;undefined&#39;)`.<br>- Variable input such as `Date.now()` or `Math.random()` which changes each time it&#39;s called.<br>- Date formatting in a user&#39;s locale which doesn&#39;t match the server.<br>- External changing data without sending a snapshot of it along with the HTML.<br>- Invalid HTML tag nesting.</pre><p>BTW, this project uses:<br>- NextJS 15.0.2<br>- next-themes 0.3.0</p><p>The component we want to render will look like</p><pre>const DefaultAppLogo = (props: React.SVGAttributes&lt;SVGElement&gt;) =&gt; {<br>  const { theme } = useTheme();<br>  const imageSrc = useMemo(<br>    () =&gt; (theme === &#39;dark&#39; ? LOGO.FULL_DARK : LOGO.FULL_LIGHT),<br>    [theme],<br>  );<br>  return (<br>    &lt;Image<br>      src={imageSrc}<br>      width={0}<br>      height={0}<br>      priority={true}<br>      alt={LABEL.SHORT_TITLE}<br>      className={cn(&#39;h-10 w-auto&#39;, props.className)}<br>    /&gt;<br>  );</pre><h4>Why this happened?</h4><p>Before that, we need to know what is hydration. Hydration happened because the HTML server-side rendered is not the same as the first time HTML loaded on the client side.</p><p>In my code, this happened because the server could not detect useTheme from next-themes so the result imgSrc is LOGO.FULL_LIGHT but on my client, the theme is set as DARK. This will cause conflict on the client side.</p><pre>                                    &lt;img<br>                                      alt=&quot;GLChat&quot;<br>                                      fetchPriority={undefined}<br>                                      loading={undefined}<br>                                      width={0}<br>                                      height={0}<br>                                      decoding=&quot;async&quot;<br>                                      data-nimg=&quot;1&quot;<br>                                      className=&quot;w-auto h-10&quot;<br>                                      style={{color:&quot;transparent&quot;}}<br>                                      sizes={undefined}<br>                                      srcSet={undefined}<br>+                                     src=&quot;/images/glchat-dark.svg&quot;<br>-                                     src=&quot;/images/glchat-light.svg&quot;<br>                                      ref={function}<br>                                      onLoad={function onLoad}<br>                                      onError={function onError}<br>                                    &gt;</pre><p>+ is HTML on the client side<br>- is HTML on the server side</p><h4>How to fix it?</h4><p>There are several ways to solve it:<br>1. Use inline class<br>2. Render it only on the client</p><h4>Use inline class</h4><p>An inline class can solve the hydration on next-themes because it will not change the HTML code on the client side. You can do this</p><pre>&lt;Component className=&quot;dark:class-name&quot; /&gt;</pre><p>The DARK value only runs when the theme is set to DARK, but the class does not need to change even if the theme is set to LIGHT. But this way does not solve my issue because it uses dynamic value from the environment file which can not be done on CSS.</p><h4>Render it only on the client</h4><p>The second way is rendering it on the client side. The component can be not rendered on the server side. We ensure that the HTML is already rendered on the client first and then update it later.</p><p>We can use useEffect to make sure the client is already mounted then we render the component.</p><pre>const [hydrated, setHydrated] = useState(false);<br>useEffect(() =&gt; {<br>  setHydrated(true);<br>}, []);<br><br>return(<br>  &lt;&gt;<br>    {hydrated &amp;&amp; &lt;Component/&gt;<br>  &lt;/&gt;<br>)</pre><p>We can also make the hydrated check as custom hooks.</p><pre>export const useIsHydrated = () =&gt; {<br>  const [hydrated, setHydrated] = useState(false);<br>  useEffect(() =&gt; {<br>    setHydrated(true);<br>  }, []);<br>  return [hydrated];<br>};</pre><p>Then we use it on each component that has the hydration error.</p><pre>const DefaultAppLogo = (props: React.SVGAttributes&lt;SVGElement&gt;) =&gt; {<br>  const { theme } = useTheme();<br>  const [isHydrated] = useIsHydrated();<br>  const imageSrc = useMemo(<br>    () =&gt; (theme === &#39;dark&#39; ? LOGO.FULL_DARK : LOGO.FULL_LIGHT),<br>    [theme],<br>  );<br>  if (!isHydrated) {<br>    return null;<br>  }<br>  return (<br>    &lt;Image<br>      src={imageSrc}<br>      width={0}<br>      height={0}<br>      priority={true}<br>      alt={LABEL.SHORT_TITLE}<br>      className={cn(&#39;h-10 w-auto&#39;, props.className)}<br>    /&gt;<br>  );<br>};</pre><p>On the code, Image component will render on the client side only. On the server side, it will return null first but it is not checked by hydration check because we have another step, the component is already mounted and client changes are allowed.</p><h4>Conclusion</h4><p>If possible use <strong>Inline Class</strong> first than use <strong>Render on Client</strong> because it is a tricky way to by pass the hydration error warning.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e58ef934f13a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Decrypt NextAuth JWT on Another Application]]></title>
            <link>https://fmrozaqi.medium.com/decrypt-nextauth-jwt-on-another-application-4398a9e3bbc5?source=rss-b8db7ae6c5e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4398a9e3bbc5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Faiz Miftakhur]]></dc:creator>
            <pubDate>Thu, 17 Oct 2024 03:59:01 GMT</pubDate>
            <atom:updated>2024-10-17T03:59:01.956Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YwPgkQCa-E0T-otonf_L6Q.jpeg" /></figure><p>There is a problem when I want to integrate NextAuth with another backend. We can’t get the user data from Next to Backend without sending it unencrypted. But sometimes, we want to use the JWT generated by NextAuth and get the data from it on another app.</p><p>First, I think NextAuth JWT is just a regular JWT. But when I try to check on <a href="http://jwt.io/">jwt.io,</a> it can’t be decrypted, so I tried to find out how to decrypt it.</p><p>NextAuth uses HKDF to get the JWT key, so the input key that we set on the environment NEXTAUTH_SECRETwill be processed first using HKDF with configuration:<br>1. algorithm: SHA256<br>2. length: 32<br>3. info: “NextAuth.js Generated Encryption Key” or “NextAuth.js Generated Encryption Key {salt}”</p><h4>How to Get JWT Raw Token</h4><p>NextAuth has the method getToken to get the authentication token, but it returns the object of the token (decrypted token). For more information, you can check this <a href="https://next-auth.js.org/tutorials/securing-pages-and-api-routes#using-gettoken">link</a>.</p><pre>// This is an example of how to read a JSON Web Token from an API route<br>import { getToken } from &quot;next-auth/jwt&quot;<br><br>export default async (req, res) =&gt; {<br>  // If you don&#39;t have NEXTAUTH_SECRET set, you will have to pass your secret as `secret` to `getToken`<br>  const token = await getToken({ req })<br>  if (token) {<br>    // Signed in<br>    console.log(&quot;JSON Web Token&quot;, JSON.stringify(token, null, 2))<br>  } else {<br>    // Not Signed in<br>    res.status(401)<br>  }<br>  res.end()<br>}</pre><p>After exploring it, it can <a href="https://next-auth.js.org/configuration/options#jwt">get the raw token by adding the value of the option</a>. We can add the option with raw: true to get the raw token.</p><pre>const token = await getToken({ req, raw: true });</pre><h4>How to Decrypt JWT NextAuth (TS)</h4><p>Requirement:<br>1. <a href="https://www.npmjs.com/package/jose">jose</a><br>2. crypto (Already installed on Node 21)</p><pre>import { hkdf } from &#39;crypto&#39;;<br>import { jwtDecrypt } from &#39;jose&#39;;<br><br>hkdf(<br>  &#39;sha256&#39;,<br>  process.env.NEXTAUTH_SECRET || &#39;&#39;,<br>  &#39;&#39;,<br>  `NextAuth.js Generated Encryption Key`,<br>  32,<br>  async (err, derivedKey) =&gt; {<br>    // checking if any error is found<br>    if (err) throw err;<br><br>    // display the result<br>    const { payload } = await jwtDecrypt(token, new Uint8Array(derivedKey));<br>  },<br>);</pre><h4>How to Decrypt JWT NextAuth (Python)</h4><p>Requirement:<br>1. <a href="https://pypi.org/project/python-jose/">jose</a><br>2. HKDF (Already installed on Python 3.11)</p><pre>from jose import jwe<br>from cryptography.hazmat.primitives.kdf.hkdf import HKDF<br>from cryptography.hazmat.primitives import hashes<br>from cryptography.hazmat.backends import default_backend<br><br>def hkdf_expand(secret: str, length: int, info: bytes) -&gt; bytes:<br>  hkdf = HKDF(<br>    algorithm=hashes.SHA256(),<br>    length=length,<br>    salt=None,<br>    info=info,<br>    backend=default_backend()<br>  )<br>  return hkdf.derive(secret.encode())<br><br>def decrypt_jwt(token: str, secret: str):<br>  info = b&#39;NextAuth.js Generated Encryption Key&#39;<br>  key = hkdf_expand(secret, 32, info)<br>  print(list(key))<br>  try:<br>    decoded = jwe.decrypt(token, key)<br>    return decoded<br>  except Exception as e:<br>    print(e)</pre><p>NOTE: We use Jose because regular <a href="https://www.npmjs.com/package/jsonwebtoken">jsonwebtoken</a>(npm) or <a href="https://pyjwt.readthedocs.io/en/stable/">PyJWT</a>(python) will check whether the token first it is valid or not. When it checks regularly it will return invalid.</p><p>In conclusion, it only describes how to decrypt the JWT from NextAuth. Actually, we can do any customization for integration of our NextJS App using NextAuth with any other Backend. If there are any better implementations, let’s discuss them in the comment section. Thank you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4398a9e3bbc5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Top-down Learning]]></title>
            <link>https://fmrozaqi.medium.com/top-down-learning-976468add0b1?source=rss-b8db7ae6c5e9------2</link>
            <guid isPermaLink="false">https://medium.com/p/976468add0b1</guid>
            <category><![CDATA[teknik-belajar]]></category>
            <dc:creator><![CDATA[Faiz Miftakhur]]></dc:creator>
            <pubDate>Sun, 18 Oct 2020 16:58:52 GMT</pubDate>
            <atom:updated>2020-10-18T16:58:52.701Z</atom:updated>
            <content:encoded><![CDATA[<p>Mumpung masih awal masa UTS nih. Saya mau <em>sharing </em>terkait metode belajar yang sering saya gunakan dalam belajar. Bukan, bukan<em> top-down learning</em> seperti yang di tulis di judul karena baru saja saya menemukan jika <em>top-down learning</em> itu emang ada tetapi beda daripada yang saya maksudkan meskipun bisa juga disangkut pautkan dengan teori tersebut.</p><h3><strong>Apa itu <em>top-down learning</em>?</strong></h3><p>Setelah saya baca di <a href="https://link.springer.com.ezproxy.ugm.ac.id/referencework/10.1007/978-1-4419-1428-6"><em>Encyclopedia of the Sciences of Learning</em></a> yang ditulis oleh Norbert M. Seel (2012), <em>top-down learning</em> ialah mempelajari pengetahuan eksplisit terlebih dahulu baru mempelajari pengetahuan implisit.</p><p>Nah apa itu pengetahuan eksplisit dan implisit? Pengetahuan eksplisit ialah pengetahuan yang sudah diterbitkan/dipublikasikan salah satunya ialah teori-teori dibuku. Sedangkan pengetahuan implisit ialah pengetahuan yang masih berupa pengalaman-pengalaman pada seseorang.</p><p>Dengan ini bisa dibilang bahwa <em>top-down learning</em> ialah mempelajari dari hal yang umum/general ke arah spesifik yang berdasarkan pengalaman-pengalaman yang ada. CMIIW.</p><h3>Mengadaptasi Koding</h3><p>Seperti yang disebutkan dalam sub-judul di atas, ide saya sebenarnya mengadaptasi dari sebuah algoritma pada pemograman. Koding sendiri ialah sebuah aktivitas menuliskan kode pada saat membuat program.</p><p>Iseng-iseng saya cari di google ternyata ide saya sudah ada yang menulis sebelumnya di Medium pula, hehehe. Ide ini mirip dengan artikel dengan judul <a href="https://medium.com/datadriveninvestor/learn-to-code-or-do-anything-top-down-bottom-up-and-other-approaches-bd2fd8eb89dd">Learn to code (or do anything): top down, bottom up and other approaches</a> yang ditulis oleh Austin Tindle (2018), tetapi saya akan coba tulis dengan bahasa Indonesia (Bukan terjemahan).</p><p>Dunia pemrograman memiliki banyak sekali teori yang mana salah satunya ialah <em>Dynamic Programming </em>atau DP. DP merupakan sebuah metode pengoptimalan matematika dan metode pemrograman komputer. Tujuan dari metode ini ialah menyederhanakan masalah yang kompleks menjadi lebih sederhana secara rekursif. Rekursi sendiri ialah proses pengulangan sesuatu dengan cara kesamaan-diri.</p><p>Dari DP ini terdapat dua buah pendekatan yaitu top-down dan bottom-up. Sederhananya pendekatan top-down memanfaatkan memoisasi yaitu menyimpan hasil yang nantinya akan digunakan lagi kedepannya. Sedangkan bottom-up memanfaatkan tabulasi yang membangunnya dari paling sederhana menjadi kompleks.</p><p>Sudah pusing? Sama saya juga mulai pusing.</p><p>Terus, apa yang diadaptasi? Setelah merenung ternyata metode ini kita gunakan dalam kehidupan pendidikan khususnya pendidikan formal. Mungkin memang sudah ada teori yang ada tetapi sampai tulisan ini ditulis, saya belum mencoba mencarinya. Anggap saja ini sebuah <em>sharing </em>pengalaman.</p><h3>Strategi Belajar</h3><p><em>Bottom-up</em> merupakan strategi pembelajaran dalam sekolah-sekolah yang mana kita belajar dari dasar. Semakin kita naik tingkat maka pengetahuan yang diajarkan akan semakin kompleks. Contoh sederhananya ialah awal masuk SD kita belajar penjumlahan, kemudian perkalian, pembagian, menghitung keliling, luas, dan volume, dan perhitungan-perhitungan lain hingga angka yang kita pelajari berubah jadi huruf saja. Hehe.</p><p>Sedangkan pada <em>top-down</em> kita membalikkan cara belajar kita dari yang kompleks ke yang sederhana. Pada pendekatan <em>top-down</em> di dalam pemrograman akan ada namanya memoisasi seperti yang disebutkan sebelumnya. Konsep dari top-down sendiri ialah memecah hal kompleks menjadi lebih sederhana. Jika yang sederhana itu masih kompleks maka akan dipecah lagi menjadi lebih sederhana. Terus menerus hingga sangat sederhana dan tidak perlu dipecah lagi. Tetapi ada kalanya meskipun apa yang kita pelajari belum sederhana tetapi kita sudah paham maka tidak perlu untuk memecah pelajaran tersebut menjadi sederhana, inilah memoisasi. Kita tidak perlu mengulang terlalu dalam, tetapi cukup hingga tahap yang kita sudah kuasai.</p><p>Tidak jarang kita tertinggal pelajaran atau perkuliahan, entah karena guru/dosen menjelaskan terlalu cepat, kita yang saat itu kurang konsentrasi, atau pun pada saat itu tidak mengikuti pembelajaran. Maka dari itu, untuk menguasai materi ialah dengan mempelajari ulang. Metode top-down yang adaptasi koding ini bisa digunakan. Saat kita belajar sebuah materi tetapi masih sulit untuk memahaminya maka coba untuk memecahnya ke materi yang sederhana dan mempelajari materi sederhana itu terlebih dahulu karena sejatinya pengetahuan kompleks merupakan pengetahuan sederhana yang saling berkolaborasi, eaaa.</p><p>Bagaimana jika kita tidak bisa memecah materi yang kompleks menjadi materi yang sederhana? Saya pernah menulis di blog saya terkait cara belajar yang benar menurut saya kala itu, dapat dicek <a href="http://restorisasi.blogspot.com/2019/01/belajar-yang-benar.html">di sini</a>. Salah satu caranya ialah dengan datang kuliah/sekolah. Kenapa? Intinya agar kita tau apa saja yang diajarkan karena yang diajarkan normalnya dari yang sederhana kemudian kompleks. Cara lain ialah dengan mencoba membuat <em>mind map</em>. Tetapi terkadang jika kita terlalu jauh ketinggalan pelajarannya, maka akan lebih dalam <em>mind map</em> yang perlu dibuat. Inilah mengapa jangan terlalu berleha-leha agar apa yang perlu kita kejar tidaklah terlalu jauh.</p><p>Jika sudah dapat poin-poin yang perlu dipelajari maka kita tinggal pelajari. Bagaimana caranya? Saya percaya setiap orang memiliki cara nyaman dalam belajar masing-masing. Maka dari itu silakan eksplorasi cara belajarnya. Ada sedikit catatan, apa yang telah kita kuasai bukan tidak perlu dipelajari hingga kita tidak menyentuhnya sama sekali apalagi ketika akan menghadapi ujian. <em>Review </em>materi juga diperlukan untuk mempertajam ingatan kita.</p><p>Jika masih belum paham mungkin sedikit kata-kata penutup ini bisa menjelaskan inti tulisan di atas. Bagi saya kita tidaklah gagal, hanya saja mungkin kita melewati sebuah level yang harusnya kita kuasai sebelum melanjutkan level selanjutnya. Sedikit kembali ke level dimana kita belum kuasai agar kedepannya kita bisa menyelesaikan level-level berikutnya dengan lebih baik dan bukan secara kebetulan. <strong>Jangan lupa belajar</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=976468add0b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>