#cpp and C++ newbie resources

1 messages · Page 1 of 1 (latest)

pale leaf
#

One of the challenges #cpp often faces is dealing with people who don't know how c++ or sometimes even basic programming works trying to jump into UE c++. Usually this results in much consternation as we all fumble around trying to figure out the actual issue and eventually linking a c++ book in a huff

#

The problem I have with this is that people get linked like, actual hardcover books they have to order or paid courses

#

I think the policy should be to prefer free resources like learncpp.com over a list of paid books

dusk orbit
#

That's why I usually end up linking learncpp.com, but you can't really control what other people do.

#

It's not like linking the book list is an "official policy"

#

Don't get me wrong - I'd love to have a better way to get people to look at resources, esp. those coming in with no experience.
Maybe a manny command to link a few things?

pale leaf
#

Hardly, it's just influenced by the pins

dusk orbit
#

I don't think it is. Most of the regulars linking those things use those links because everyone else does, not because anyone is actively looking at pins.

#

But if we could instead maintain a manny command or something imo that'd be better

pale leaf
#

True

dusk orbit
#

Having a manny command is probably enough to get regulars to use it when someone needs resources since they won't have to go searching for the link they usually give out. And it means people won't pick and choose which resources to link (unless there's something specific they want to show)

pale leaf
#

I do think ue++ resources are rather frustratingly spread out

#

Like with samrr's uobject issues

#

I don't even know if we have a specific page to show

marble depot
#

I am contemplating building a readme/YouTube tutorial on the suggested way of learning unreal engine programming, etc. Start with the *BASICS and move forward from there.

rich pendant
#

If you guys have suggestions, please let me know!

marble depot
rich pendant
#

But I'd love to hear suggestions from the community. When Manny v2 releases, there will be an easy way for anyone to submit suggestions, so it will grow over time. 🙂

#

I've seen this style of command work very well in other dev communities. It's basically an easy way for members of the community to share pre-written responses to common questions instead of having to type them every time.

#

Here's an example.

Discord_AiYareVRuM.gif
pale leaf
#

Oooh

#

I like it

#

Could you pm Manny this question as well?

rich pendant
#

In theory yes, but right now the command is designed to be server-only.

#

It's meant to be an easy way to respond to someone else.

#

I can also add the ability for Manny to mention the person you're replying to. 🙂

pale leaf
#

Could it even link to specific discord messages in the past?

rich pendant
#

Hypothetically, yes. That's dicey since they can be deleted. What do you have in mind?

pale leaf
#

Discord as a wiki is evil but there have been some nice discussions I sometimes revisit

#

So not ideal of course

rich pendant
#

Ah. Yeah if there's a useful nugget that someone should know, i.e. something you might pin, I'd prefer to codify it as answer you can summon with this command, instead of linking to a potentially missing convo.

#

Plus, the new website will also be getting a resource section.

#

Should compliment the Discord server nicely for stuff like this.

stoic wyvern
rich pendant
primal herald
#

we definitely need a command to link to common c++ learning resources, like the learncpp.com and the books list possibly, and the converting bp to c++ unreal course

#

also can we please have a command that explains people how to ask questions.
Like include error message / exception (possibly callstack / locals), use output log, post offending code, say what you expect and what is the incorrect result. And explain how to post code blocks with highlighting.

#

although less relevant now that ue5 is by default live coding but still

fast arrow
#

doesn't ue5 use live++ for hot reloading? I thought it's not relevant anymore

pale leaf
#

We still see hot reloaders occasionally

#

Although they are petering out

dusk orbit
#

and the site may need updating to point out that live coding isn't without its faults either... livecodingisntperfect.com anyone?

fast arrow
#

Well to turn people away from something that is listed as production ready from both the developers (live++), and implementers (epic) probably is not the best thing. There doesn't seem to be an easy to find (or any) known issues page so if there was anything to point to it would probably be something more along the lines of that, along with some advice like YMMV, and don't use it expecting to never build your project again

dusk orbit
#

It's "production ready" in the sense that it works, but native code reloading is inherently swarmed with asterisks. The problem is Epic themselves don't warn you about these issues anywhere and even when hot reload was the default and was actively corrupting people's assets they still didn't put any warnings anywhere.

#

So I don't think any appeal to authority like "but the live++ guys and epic said it's ready!" is worth anything. Anyway, this is somewhat off topic - the point is to have a place for common resources, details about what belongs there is something to be decided later I imagine.

fast arrow
#

And I'm not saying that because they say it's ready to go all in, I'm saying to document those asterisks and point people to them instead of pointing them to a semi-meme website that gives the message of do not use at all. A lot has changed in the last 2 years and is continuing to change every day

dusk orbit
#

hotreloadsucks.com is fine because the state of hot reload will forever more be as that website states.

#

And the website also links to a wiki page that's updated a bit more frequently.

fast arrow
#

Of course and if anything it was more hinting that the site should be changed to reflect things are different now. And I'm sorry but to say that any technology will stay in any state forever is simply not true

dusk orbit
#

Things aren't different though

#

hot reload != live coding

#

hot reload, the system UE4 has on by default, is not under active development because it's being replaced by live coding.

fast arrow
#

yes its being replaced by live++, a company dedicated to the single product

dusk orbit
#

so I fail to see what your issue is

fast arrow
#

so I guess my mistake is thinking that you were referring to live coding as hot reloading, them being the same thing

#

so my bad for that

dusk orbit
#

Right. They're completely different systems - hot reload is the old system that broke assets all the time, live coding is epic's implementation of live++.

#

live coding is much better but unfortunately has picked up a few of hot reloads old issues in the process 😦

spring wasp
#

even after about one years of UE C++ programming I never was ablt to make it work as I wanted x)

empty oar
pale leaf
#

Omg, this is exactly what I wanted

#

Sticky it!