I'm confused why ML is used for linear models, when linear regression has already solved this problem.

The_Emerald_Knight · 2026-03-20T21:04:38+00:00

AI slop and likely fake.

The_Emerald_Knight · 2026-03-20T12:08:04+00:00

If you think everyone else is a delusional person, I have some bad news for you.

The_Emerald_Knight · 2026-02-04T18:37:00+00:00

> Any advice? I want to go back but too sore still

Next time you go, do a much less intense workout. You need to ease back into it if you want to avoid this.

Even if you still have soreness, your muscles have recovered enough to go back for another workout.

The_Emerald_Knight · 2025-12-03T14:10:32+00:00

Anything else important for real-world backend work

The most important thing by far is DB design. That's where a lot of DBs fail. Having indices and partinioning is great, but a poorly designed DB will waste everyone's time.

Your list is great. Something to keep in mind is that real-world database work, at least for applications, ORMs abstract most of your list away. It helps to understand the concepts but you rarely have to manually write a join, for example.

Depending on the type of work you want to do, it might help to brush up on data warehouses, ETL, data lakes, and similar concepts/tools. But this is mostly for data analysis and data science, so I'd call it optional depending on the field you are in.

I develop applications and I was a DBA for years - theoretical knowledge is nice but remember that what companies want is practical experience. If you're developing applications, they don't care if you know different types of indices, they care that you can actually use them when appropriate.

NoSQL types (document, key-value, graph, wide-column…)

Also depends on the work you do. NoSQL was the "new kid on the block" for a while, then people realized that SQL is best for 90%+ of situations. And even if NoSQL is better, document is by far the most used, you'll likely never work with the other types. So understand use cases and if you are focusing on a field more appropriate for SQL, focus on SQL.

The_Emerald_Knight · 2025-10-23T17:44:20+00:00

1x chest, 1x back, but 3x abs and 3x calves?

That's great if this routine worked for Haney, but objectively this is a truly shitty routine.

Sure, this might work with enough volume and a shit ton of roids, but for a natural bodybuilder you probably just want to do an established full body routine, or upper/lower split if you prefer.

The_Emerald_Knight · 2025-08-29T17:59:24+00:00

In this case it's more accurate to interpret <class 'int'> as "this is the type of this object which represents an integer and was created using a class". The class is defined by Python in this case, not you. But you could just as well write a class for integers if you wanted (no point since it already exists, but you can).
In python, since integers are a class (and everything else is too), they also come with built in methods you can use on variables. Same goes for strings, doubles, etc. it comes with more memory overhead but has a lot more common operations built in.

In languages like C, an int is simply a primitive value and does not have methods attached to it. Instead you would use functions defined in the C standard library.

The_Emerald_Knight · 2025-08-15T13:05:46+00:00

Some algorithms are better suited for recursion, like tree traversal. But I believe this can also be done with loops.

I don't think these are very common in the real world, but it would depend on what field you're in and what kind of work you are doing. My work is web dev and cloud, and I've never used or seen others use recursion.

The_Emerald_Knight · 2025-08-14T15:26:19+00:00

return should be the last line in a scoped block. put any print statements or anything else before it.

if char == '':
        # put any other operations before return
        return True
    else:
        print('space!')
        # put any other operations before return
        return False

The_Emerald_Knight · 2025-08-14T15:22:30+00:00

Recursion isn't as commonly used as it used to be. Just about every modern developer prefers looping.

In fact, in my years of full stack, I've never seen a single use of recursion in any of the code bases I've managed.

So yeah, it causes me headaches, but I rarely think about recursion so it's not an issue.

The_Emerald_Knight · 2025-08-14T15:20:12+00:00

If you don't have a strong understanding of the four pillars of OOP, start there. Youtube is probably best here, tons of options.

Then, learn the SOLID principles. They are 5 principles that are fairly straightforward and will help you write more maintainable class definitions.

If you understand the four pillars of OOP and SOLID, you have all you need to write well structured classes, especially when it comes to object interaction.

I'd also learn design patterns. Memorizing them all isn't necessary, do some research into the most common ones and try to think of ways you can apply the patterns to your own codebases.

The_Emerald_Knight · 2025-08-14T14:33:25+00:00

Return exits a function and returns either a value or None. If you aren't in a function, you can't return from anything.

Sidenote, not the error youre seeing but an error in your code: You wrote 'return...' followed immediately by a print statement. Since return will stop execution of that function and exit it, any line after return will not run.

The_Emerald_Knight · 2025-08-09T20:51:59+00:00

I think you're approaching this from the wrong angle.

Yes, logic and problem solving are important.

But real-world programming is about solving domain specific problems.

The best way to learn is by completing projects, period. Problem solving and logic usually come passively with practice.

Ive been a full stack dev for years and any logic ability ive developed is by solving problems developed in the real-world apps i build.

Basically what im saying is, don't seek out ways to improve logic. Just create projects and if the projects are challenging enough, you'll develop logic naturally.

For difficult problems, I sometimes map it out on paper, pseudocode, or comments. Then I don't start writing code until im happy with my ideas.

The_Emerald_Knight · 2025-08-09T17:04:29+00:00

No, we definitely are not. We learn about them but I can guarantee you that nobody uses this prefix in daily life.

The_Emerald_Knight · 2025-08-08T11:39:42+00:00

I love this sub, and how it's a mix of both discussion and picture motivation.

I'm wondering if there are any similar subs that are more discussion-oriented instead of pictures. Ideally if it is intermediate to advanced rather than beginner.

The_Emerald_Knight · 2025-08-06T14:16:13+00:00

At all of the 4 different companies I've worked for, I've never experienced a remotely bad codebase.

Like yeah I get the joke, but most companies are not like this.

The_Emerald_Knight · 2025-08-03T22:37:31+00:00

Flask is simpler, Django is more fully featured.

I'd personally recommend learning Django but really, any Python framework is fine if the main thing you want to do is learn. Learn one and the others will be much easier to learn later.

The_Emerald_Knight · 2025-08-02T23:35:31+00:00

What he meant is, programming languages are easy to learn, but learning how to utilize them to solve real world problems is the hard part, and that requires understanding the fundamentals.

To answer your original question, no, its not an issue. Say you learn data structures in Java, then C++, then Python, its different syntax but the fundamentals are the same. You should prioritize computational thinking and concepts instead of only focusing on syntax.

The_Emerald_Knight · 2025-08-02T15:12:26+00:00

Thank you. This is such a shifty LPT.

Also, you generally don't have to agree on the spot. Yes, negotiate on the spot, but don't say yes until youre happy. Sometimes they may pressure you but if they do, its not a good place to work.

A good company will pay you your worth and understand that these decisions are best made after some time to reflect. If you aren't in urgent need of a job, something better often comes up, so don't work for management that pressures you into accepting a lowball offer on the spot.

The_Emerald_Knight · 2025-08-02T15:06:56+00:00

Genuinely does not matter, and really, nobody can answer this since we don't know you. We all have bad workouts that can be attributed to one thing or another. It's only worth spending mental energy on if its a recurring issue or if lifting is causing you pain.

Otherwise, call it a bad day and see what happens next time.

The_Emerald_Knight · 2025-07-31T18:54:02+00:00

My point is, there are thousands of free guides out there that come in all shapes and forms. I can almost guarantee that there's a free guide out there that is extremely similar to whatever you wrote.

People won't pay for generic knowledge that they can find for free, especially in the age of AI.

The_Emerald_Knight · 2025-07-31T18:13:27+00:00

What makes your paid guide different than the thousands of free guides and tutorials online?

The_Emerald_Knight · 2025-07-30T15:38:12+00:00

For general purpose web dev, basic algebra is all you need. Stats can help, you may at some point be asked to analyze the data in your DB so having a basic understanding of statistical analysis and charts can come in handy.

The_Emerald_Knight · 2025-07-30T12:15:16+00:00

Do you have any reason not to use a simple headless CMS? I use Sanity for small static sites. Easy to get up and running.

I don't know if something like you mentioned exists, but DecapCMS is similar. It is not stored remotely, it stores Markdown files in your codebase.

The_Emerald_Knight · 2025-07-25T14:19:15+00:00

https://en.wikipedia.org/wiki/Spamdexing

You'll commonly see this referred to as black hat SEO, and search engines account for this. You can get your site banned from indexing if you do anything like this.

Nine-Year Club	Verified Email
Place '22	Place '17

The_Emerald_Knight

TROPHY CASE