1,557 karma · joined April 20, 2022
Could you give me a link please? The Godot editor itself can't do multi-window and I haven't found a clear explanation on how to do that in the games either.
> You should be using C# for stuff like that. Ignore the Godot API, just use .NET 8.
I use the non-dotnet version of Godot, I'm not happy with the confusing licensing Microsoft has put around .NET [1]. If anything, I'll go the gdextension route, but it hasn't been painful enough yet to do that. For a UI you couldn't ignore the typing system since you'd need to feed the data into it and read from it a lot.
The other problem with Godot specifically is that every thing is tied to GDScript/the Godot typing system (yes, even the C# and gdextension APIs) and you need to deal with its inconsistencies. I'm currently implementing something as simple as a schema validator (think JSON schema) and it's nightmareishly tough in comparison to any other language I have implemented this in. And then we are not even talking about the almost universal lack of error handling in a large portion of the built-in functions, or really silly things like that opening a TCP connection apparently requiring active polling. I could go on.
I love Godot, it's super simple to build game-related things with, but holy macaroni do I wish they had thought things through just a little more when they implemented them. I would never want to build a data-heavy desktop app in Godot.
I built ContainerSSH at that time too to learn Go (look up the first versions, it's ridiculous how small they are) and then went to work for Red Hat with my new found knowledge.
I can only speak from my experience, but what helped me land interviews ( as a gradually built up over the last 3-4 years) was:
- Having contributions in high profile open source projects name-dropped at the beginning of my CV. (Front-load the interesting stuff. Also, these should be substantial works in case somebody goes to check.)
- Having relatively well-known open source projects I built from scratch (ContainerSSH, gotestfmt, etc) in my CV with well-known users I can also name drop. These projects had nothing to do with my day job and I built them in my free time.
- Having spoken at several conferences. This is the most unfair of all since not everyone can travel and having the conference in there doesn't say anything about the quality of the talk, but it seemed to help get through the recruiter filter.
What helped me get through the interviews (again, from my experience):
- Having experience in diving into unknown codebases and problems. Most companies that are serious about coding will have you do live coding, take home exercises, or read some code in the interview. If you do enough work on open source stuff, you'll develop this automatically as you will be jumping into code that's not yours.
- Being able to do TDD in the live coding interview and still finish on time. Nobody I talked to actually does hard core TDD in the industry and most people are stuck with a ton of legacy code, but this is a magic trick that will get you some eyebrows raised assuming you don't mess up the rest of the interview. Also, forget algorithmic problem solving. While at least knowing algorithms and datastructures helps, most companies don't have deep algorithmic problems in their day to day operations, so encountering these in the interview I found to be a minor red flag.
- Knowing the language basics. If it's Javascript, know your type issues or how the runtime works. If you do Go, know parallelization problems and how to solve them.
- Structure your code! On the interviewing side I had to fail too many candidates for submitting code with an unclear/messy structure for take home exercises.
Big no-nos (when I was the interviewer):
- Do not claim you contributed to a project if all you did was a typo fix.
- If you have a Github profile, make sure it's not full of forked repos you didn't contribute to. I will only look at what you linked in your CV, but others will google your name (no matter if it's illegal or not).
- Clean up or set your social media to private if you don't want interviewers to see that. Google yourself, make sure there are no red flags there.
- Don't use ChatGPT/Copilot without heavy refactoring. This is incredibly easy to pick out and not cleaning it up, not making the code style consistent screams that you have no idea what you are doing. Remember, interviewers only have your code to go by as a signal source.
- If there is a woman in the interview panel, make sure you don't just address the guys. We did interviews with my wife and we noticed this a lot. This may just be a force of habit, but for companies paying attention to diversity, this is an immediate red flag. The people who got flagged for this usually turned out to have a culture fit problem in other areas too, but it's worth keeping in mind.
- Leave your ego at the door. They may criticise your code, but don't get defensive! Stay factual, that will help defuse the situation.
- Don't have typos in your CV. Use a spell checker.
Finally, really, don't give up. My experience is just that of one person, I (probably) don't live in the same country, probably don't have the same amount of time available as you do, and I (probably) don't work in the same area as you. My advice may be complete garbage and not applicable to your situation.
I used to work for Red Hat (OCP on oVirt/RHV, Arcalot/Arcaflow, etc), in a little over 2 years I wrote somewhere around 40.000 lines of code that I can account for with 80%+ time spent, but that diminished greatly around the end as a lot of changes into the "Scrum to rule everything" direction happened, which decreased the amount of code produced by a lot.
Depending on what you do you may want to go window shopping for jobs where coding skills are valued and that are low on process. If the interview process already puts heavy emphasis on your code, that may be a place for you. If, on the other hand, the quality of your code isn't appreciated as long as it works... Smaller companies/projects tend to work better.
If you don't like it, Python is a very reasonable choice as it is very much in demand.
> Some SSH implementations such as OpenSSH or Tectia support other ways to authenticate users. Among them is the certificate-based user authentication: only users in possession of a certificate signed by a trusted certificate authority (CA) can gain access to the remote server [12]. Available for more than 10 years, this authentication method requires setting up a CA and distributing the certificates to new users and is still not commonly used nowadays.
Somebody had an agenda to make SSH look as bad as possible. You can implement OIDC authentication with keyboard-interactive, no need for HTTP/3 for that. However, it gets very tricky if you want automated / script access, so it doesn't solve the authentication problem.
As an aside, Tatu Ylonen, the original author of the SSH protocol, published a paper in 2019 titled "SSH Key Management Challenges and Requirements"[1], which is an interesting read. It would seem the authors of this paper should have at least read it.
A lot of papers seem to try and extract 3D data from 2D pictures since the dataset is just so much better, but that hits obvious limitations. And we aren't even talking about any animations yet, which anyone who ever tried making them by hand knows, add a huge jump of complexity because you are not just morphing individual vertices, you actually want them to move consistently or else the faces are going to start doing weird glitchy things. Generating 3D stuff is less like generating pixel-based images and more like generating an SVG where the shapes actually make semantic sense, but a lot more complex. (Which, as far as we have found, no AI has managed so far either.)
Sure, you'll start seeing animated faces, architectural plans, and you'll also see bone system, based animations for humanoids (humanoid 2D video to 3D bone animation AIs exist today), but don't expect to be able to prompt your way through creating a Pixar movie.
However, I'm happy to be convinced otherwise.
The only downside is the per-file versioning, the update needs to be run on the top directory otherwise interesting problems happen.
function new_foo(dependency) {
return function(bar) {
// Do something here
}
}The average user is very, very far away from being able to use a nearly irreplacible item for communication. And yes, it's irreplacible since there is no rollover mechanism in just publishing the public key.
My 2 cents: just say it as it is. Your manager doesn't need you having a burnout all if a sudden any more than you do.