Programming thread

[Owlbear]

Don't bother. Just steal one from Pajeet and study the latest interview questions going around. Once you're in to one job, simply say "yes, saar" anytime your boss asks you to do something and spend all day looking for a new job. If you can do this without getting fired for 6 months a couple of times, the rest is gravy.

If you're feeling ambitious, hire a Pajeet to do your job while you show up to meetings, and maybe get a second job at the same time.

 

[${Sandy}]

Guys how do I make the slamming awesome CRUD ap that'll get me all those cushy entry-level remote jobs

This but unironically

Don't bother. Just steal one from Pajeet and study the latest interview questions going around. Once you're in to one job, simply say "yes, saar" anytime your boss asks you to do something and spend all day looking for a new job. If you can do this without getting fired for 6 months a couple of times, the rest is gravy.

Faggot mindset. Do your fucking job or stay home and get niggercattle bux from the great satan so actual people don't have to tolerate being around you.

 

[Owlbear]

This but unironically

Here's my guide:
0. Graduate from a top 50 college and skip this bullshit. If not, proceed to 1.
1. Get an idea. That idea should hopefully be something easy. Preferably something related to your hobbies or other interests. For how simple this project is, the bullshit involved is going to take you hours, so you had better have fun with it.
2. Figure out what your CRUD app is going to do and split up the frontend and the backend.
3. Make a backend for your shit. Node or Python, but if you want to be a tryhard use Go. If you want to be a faggot, use Rust. Deploy in AWS lambda or a cloud free tier. If you insist on a database, use SQLite on your VPS. Most of these "CRUD" resume projects don't actually maintain state (so they aren't really "CRUD"), and just use serverless. If you can afford to, don't use a backend and just push all your shit to the frontend and you will thank yourself.
4. Pick up a frontend framework like react or nextjs and write some HTML and some JS for your frontend. These are retarded languages for retards, but frontend engineers are usually failed artists with room-temp IQs and "react" sounds like "technology" to them. If you don't use a framework, you are probably smarter than them (caveat - if you're doing something very frontend-heavy, the frameworks are better than vanilla JS), but you are not "legit" enough. Make a pretty website. There are lots of tutorials on youtube for this. Host on Vercel or your VPS, or throw it on Github/Cloudflare pages.
5. Make sure it's not completely broken.

There you go, now take your poo to the loo and get your entry-level job.

 

[macrodegenerate]

Guys how do I make the slamming awesome CRUD ap that'll get me all those cushy entry-level remote jobs

The first thing you need is a vision of something you want to make. Something basic. It can be a search engine, or a shipping website just something a normal person could use.

Now you start, and plan your project to do as little work as possible.

For your frontend you are going to learn react/Typescript/JS. You should just pickup a react template and work from there. Don't be afraid to drop $50 on a decent frontend template you don't want garbage, and time is money.

Your backend is going to be where things get a little more complex. You have several options for your backend controller, and will want to use REST as it is in vogue. You have the options of Python/flask, ASP.net, or Spring with a JVM language(Java/Kotlin/Scala). Once you've selected your backend controller. It's time to move on to Infrastructure.

You will learn how docker compose or Kubernetes works. This is non-negotiable in today's job market. All of the infrastructure you need will be deployed through one of them. You will deploy all of your services and infrastructure locally through them while developing.

For CRUD you must first determine how you will store your data. There are drawbacks and benefits to NoSQL(Opensearch/Elasticsearch) and SQL(PostregSQL). Most of them are performance based. Just pick one and stick with it. Performance doesn't matter on a portfolio project.

You will find and use every already existing implementation for functionality you can. You may wish to store files. Use Minio's S3 storage for this. You may need a username/password system, use Keycloak with its rest api. I'm sure there are other systems you can leverage for your project. Seek them out and find them. Cobble everything together and implement everything you can't find, and you have an app.

 

[Owlbear]

I'm sure there are other systems you can leverage for your project. Seek them out and find them. Cobble everything together and implement everything you can't find, and you have an app.

This is the critical part of resume-building projects, moreso than anything we have listed about technologies (they are good suggestions more than hard rules). This sentence is the name of the game. Find shit on the internet and cobble it together. You're not building Google and you're not sending people to the moon. If it barely runs, it's perfect. Maximize your return on time if you're just doing this to have something to show a hiring manager.

 

[SFWA Person of Interest]

Faggot mindset. Do your fucking job or stay home and get niggercattle bux from the great satan so actual people don't have to tolerate being around you.

Don't let me touch a nerve. I'm just accurately describing your competition. I didn't even mention the H1B part.

 

[${Sandy}]

Don't let me touch a nerve. I'm just accurately describing your competition. I didn't even mention the H1B part.

No nerves were touched lol. I just like shit talking script kiddies that cobble together niggerlicious pajeetware instead of actually putting in the effort to learn.

Speaking for myself though, I've been working really hard at learning to program and I generally try to avoid copy pasting something from the internet unless its boiler plate stuff. But that efforts payed off. I'm by no means an expert but I started learning to code back in October last year and I'm already doing entry level freelance work. I genuinely have disdain for incompetent bullshitters, because this stuff can be pretty difficult sometimes and I take pride in the effort I put in to actually learn and get good at it.

 

[Lemurakk]

Im making some progress learning Ruby but alot of the materials I found are just reading and I am a hands on kind of guy when it comes to learning.

To anyone here that knows Ruby, what is a project that you recommend that will cover all the basics? Like by the time I finish the project I will have a firm grasp on the basics for Ruby and then I'll go from there. Im learning it specifically for shopify's api.

Along with what GhastlyGhost said I would also add learning how services work and how to connect to APIs and also how gems work and how to read them, all this assuming you're using Ruby on Rails, and not sinatra or plain ruby, as you should. Services and API integration is really common and used in almost every project, while gem unpacking and reading of the gem code itself is very useful when working with old outdated gems in old codebases and will save you a lot of debugging time.

Slight PL but I actually work with Ruby every day so if you have any questions don't hesitate to ask here or via PM.

 

[${Sandy}]

Along with what GhastlyGhost said I would also add learning how services work and how to connect to APIs and also how gems work and how to read them, all this assuming you're using Ruby on Rails, and not sinatra or plain ruby, as you should. Services and API integration is really common and used in almost every project, while gem unpacking and reading of the gem code itself is very useful when working with old outdated gems in old codebases and will save you a lot of debugging time.

Slight PL but I actually work with Ruby every day so if you have any questions don't hesitate to ask here or via PM.

I ended up learning a ton trying to set up SQLite3 and Rails. Fucking rails 7.2.0 wasn't installing right so eventually I typed in to the command terminal, "gem install rails -v 7.0.0" and that worked. This shit is gonna be alot of work so I will definitely pm you when I run into anything that I get stuck on.

So far I did a little practice learning the basic syntax, and I spent a few hours installing rails and SQLite3 which was a pain in the ass great opportunity to learn new things.

Edit: For any Future Kiwis looking to learn Ruby, I found this site https://try.ruby-lang.org/

 

[Horribadger]

The first thing you need is a vision of something you want to make. Something basic. It can be a search engine, or a shipping website just something a normal person could use.

Now you start, and plan your project to do as little work as possible.

For your frontend you are going to learn react/Typescript/JS. You should just pickup a react template and work from there. Don't be afraid to drop $50 on a decent frontend template you don't want garbage, and time is money.

Your backend is going to be where things get a little more complex. You have several options for your backend controller, and will want to use REST as it is in vogue. You have the options of Python/flask, ASP.net, or Spring with a JVM language(Java/Kotlin/Scala). Once you've selected your backend controller. It's time to move on to Infrastructure.

You will learn how docker compose or Kubernetes works. This is non-negotiable in today's job market. All of the infrastructure you need will be deployed through one of them. You will deploy all of your services and infrastructure locally through them while developing.

For CRUD you must first determine how you will store your data. There are drawbacks and benefits to NoSQL(Opensearch/Elasticsearch) and SQL(PostregSQL). Most of them are performance based. Just pick one and stick with it. Performance doesn't matter on a portfolio project.

You will find and use every already existing implementation for functionality you can. You may wish to store files. Use Minio's S3 storage for this. You may need a username/password system, use Keycloak with its rest api. I'm sure there are other systems you can leverage for your project. Seek them out and find them. Cobble everything together and implement everything you can't find, and you have an app.

I do actually have basic React/javascript knowledge and have deployed a few pieces of shit to Vercel (frontend only though, I don't fucking understand how to use their database systems). It's more about finding something to do with that knowledge that'll actually get my foot in the door. Learning Kubernetes or docker does seem like a good idea and I'd been wondering about how to handle user accounts and such. Time to get cobbling I guess

 

[${Sandy}]

Normally I post here asking for pointers because you guys are helpful and I'd rather turn to a counter culture community before using mainstream channels because I have that punk rock mindset. I mean real punk rock and not those faggy sell out posers who think Blink-182 is a good band and your pronouns are valid.

I wouldn't work for a large tech company or some faggy soy startup that will get bought out by google, I won't do it even if you put a gun to my mothers head.

So here is a question I want to pose to my fellow kiwi programmers, Aside from templeOS, What is the most punk Rock coding language. What is the middle finger of programming?

What coding language is on the same vibration on this song?

 

[analrapist]

What is the most punk Rock coding language. What is the middle finger of programming?

Punk rock is conceptually simple, fast, uses the most common tropes, rejects the overcomplication of "progressive rock", is often a contentious pick, and as a style, is probably older than anyone in this thread.

Therefore, C is the most punk rock language.

 

[${Sandy}]

Punk rock is conceptually simple, fast, uses the most common tropes, rejects the overcomplication of "progressive rock", is often a contentious pick, and as a style, is probably older than anyone in this thread.

Therefore, C is the most punk rock language.

This gives me the motivation to learn C.

 

[analrapist]

This gives me the motivation to learn C.

Incidentally, you disclaimed "TempleOS" as being an obvious choice, but TempleOS is written in... HolyC. So "TempleOS", ie. HolyC, is the Hardcore Punk to C's Punk Rock.

 

[macrodegenerate]

Normally I post here asking for pointers because you guys are helpful and I'd rather turn to a counter culture community before using mainstream channels because I have that punk rock mindset. I mean real punk rock and not those faggy sell out posers who think Blink-182 is a good band and your pronouns are valid.

I wouldn't work for a large tech company or some faggy soy startup that will get bought out by google, I won't do it even if you put a gun to my mothers head.

So here is a question I want to pose to my fellow kiwi programmers, Aside from templeOS, What is the most punk Rock coding language. What is the middle finger of programming?

What coding language is on the same vibration on this song?

This is your career, don't be a retard and go out learning a cool rebel language to stick it to the man.

Learn Python for backend and JavaScript for frontend if you want freedom from strong typing, and a number of approaches to coding.

The establishment is Java/React for custom software and PHP/Javascript for WordPress, and you can make money easily with those.

 

[Looking Glass]

Normally I post here asking for pointers because you guys are helpful and I'd rather turn to a counter culture community before using mainstream channels because I have that punk rock mindset. I mean real punk rock and not those faggy sell out posers who think Blink-182 is a good band and your pronouns are valid.

I wouldn't work for a large tech company or some faggy soy startup that will get bought out by google, I won't do it even if you put a gun to my mothers head.

So here is a question I want to pose to my fellow kiwi programmers, Aside from templeOS, What is the most punk Rock coding language. What is the middle finger of programming?

What coding language is on the same vibration on this song?

Picking a language like that is retarded, and most useful ones are full of faggots anyway.

Pick and learn based on what kind of work you want to do. Don't tie yourself to one language either, most concepts you learn are very transferrable. I've used a bunch over time. Currently I mainly use C++ but thats not a recommendation.

This is your career, don't be a retard and go out learning a cool rebel language to stick it to the man.

Learn Python for backend and JavaScript for frontend if you want freedom from strong typing, and a number of approaches to coding.

The establishment is Java/React for custom software and PHP/Javascript for WordPress, and you can make money easily with those.

Do not use python on the backend. Even javascript would be better.

 

[${Sandy}]

Incidentally, you disclaimed "TempleOS" as being an obvious choice, but TempleOS is written in... HolyC. So "TempleOS", ie. HolyC, is the Hardcore Punk to C's Punk Rock.

Good point.

This is your career, don't be a retard and go out learning a cool rebel language to stick it to the man.

With that attitude, I imagine you will say please and thank you to men that fuck your woman without a condom.

--
Two codes of C
One for God and one for me
Drown out the pain from pajeet code
And flaming gasoline, until we're clean

Two dead glowies
One for hope and one for peace
Watching government lies
Leak into your empty eyes
From the TV and sinners history

 

[Concentrate Juice]

This gives me the motivation to learn C.

It's kind of a meme to recommend K&R's second edition "The C Programming Language" (direct link) to learn C, it's definitely interesting but it also does not teach you newer features of C or justify the purpose of a lot of things, it is however; a good shallow introduction to C, enough to get you going so long as you have a text editor and access to a C compiler (add the -ansi flag if you use gcc or clang, it will be more compatible with the book).

If I was gonna learn C again today, I'd go with Modern C by Jens Gustedt (direct link) because of the depth at which it covers everything you need to be a good C programmer, but it is lengthy and there is a lot of information that might just slide off without some prior knowledge of C. You don't need to read the whole thing, but at the very least, scroll through the takeaways section and read any entry that interests you or that you find yourself disagreeing with.

Good luck on the C journey.

 

[Anti Snigger]

It's kind of a meme to recommend K&R's second edition "The C Programming Language" (direct link) to learn C, it's definitely interesting but it also does not teach you newer features of C or justify the purpose of a lot of things, it is however; a good shallow introduction to C, enough to get you going so long as you have a text editor and access to a C compiler (add the -ansi flag if you use gcc or clang, it will be more compatible with the book).

If I was gonna learn C again today, I'd go with Modern C by Jens Gustedt (direct link) because of the depth at which it covers everything you need to be a good C programmer, but it is lengthy and there is a lot of information that might just slide off without some prior knowledge of C. You don't need to read the whole thing, but at the very least, scroll through the takeaways section and read any entry that interests you or that you find yourself disagreeing with.

Good luck on the C journey.

I stand by K&R as far as “canonical” C

 

[Jones McCann]

C isn't punk, C is mainstream. The real historical punk languages are the functional languages that were overshadowed, but these days they're more mainstream, i.e. more hipster than punk. The real modern punk languages are the ones that don't even want to be good like python brainfuck, eschewing the meritocracy of languages that want to be usable and saying fuck you instead. If you want my advice, learn them all.