1

Welcome to the lab!

 1 year ago
source link: https://lab.metz.sh/welcome-to-the-lab
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Welcome to the lab!

This is the new corner where I hang out, my new place!

The old one's landlord was pretty good but the place itself had too many rules and I couldn't install my art pieces there, not without a fight.

I am working on something on the side where I use interactivity and visuals to convey complex ideas. And what better place to start with than my journal!

What?

Next JS
Static Generator
Stitches props to components
getStaticProps
Provides props
Events
getArticleList
Returns required props
pages/
Content directory
index.tsx
Homepage

Why waste time say lot word when few word do trick?

– Kevin Malone

Neat right? Think of it as a quine, except it's an explaination about itself. This playground is a simple abstraction of how this site's homepage gets rendered, what functions gets used, who does what.

Oh and one last thing, the playground is actually running the code. I haven't programmed any specific animation, any specific interaction.

In fact it's this code that's being executed:

function index(props: Object) {
    return 'Sweet sweet html';
async function static() {
    const props = await getStaticProps('Get frontmatter and link to display');
    index(props);
async function getStaticProps() {
    const props = await getArticleList('src/pages');
    return props;
async function getArticleList(path: string) {
    const files = pages('Fetch all mdx file paths');
    return `
        props: {
            articleData: {
                frontMatter: FrontMatter,
                file: string,
function pages(instruction: string) {
    return [
        'src/pages/1.mdx',
        'src/pages/2.mdx'


I have always loved sharing what I am building and how, but always felt limited by the chosen medium.
There's no way I am becoming a tech "TikTok"er or YouTuber, that leaves me with just words.


Now words aren't bad, they can do magic but nothing excites an engineer's monkey brain neurons like some
good diagrams.


There are two issues that still remain:


Freeform writing is, well freeform. You barely choose a structure and execute it.
Not saying all technical writing is freeform but holy hell, a lot if it is.
As a "writer" you know what you want to talk about and how, but for the audience
it's a jail.
Firstly, how deep and stuctured you want to be has no rules, hence one can make mistakes
and might not check all the boxes, subconciously ofcourse.
Secondly, your structure might not be an easy path to traverse. A wall of text, however
eloquently written is still a wall, the amount of details you add would then mean nothing.
Hence, the resolution of information shared is quite flaky, sometimes it can be 240p with no
subtitles and once a blue moon it's 4K.


Which brings me to this place. I always envisioned and hoped the way engineering knowledge is represented
to get better, and that's what I am working on.


The lab is where I experiment with this idea, and work with you to understand how this can be beneficial to all of us.


I will be converting my old posts to this new format, writing some new ones as well and finally once and for all show why NodeJS is not single threaded!


Be seeing you!

        

        

            

                report
            

        

    







        
Recommend

        



                

    
About Joyk

    
 





Aggregate valuable and interesting links.

Joyk means Joy of geeK