Grab a sub at Start Learning at Treehouse for Free. They're front end stuff is solid. Do their front end track. I did it about a year ago. Way more value for your money than buying an individual course on css, then JS, then html, etc etcLooking for fundamentals to build sites. WordPress, CSS, JS - it's been a long time since I did any of that seriously.
Like I said, mostly web development, site building stuff.
dot net core 3.1 is OUT
LTS BABY!!!
I don't see the purpose for a github in terms of determining an applicant usefulness. I have one for the shit i did for the board migration, but I would never put anything professional there.
it is also a generational thing. So boomers don't have them, zoomers do.
Are you asking them typical CS algo questions? Program a stack, graphs, etc etc?Github is pretty much just good to have for a Junior engineer. Even then it doesn't prove anything. I'm sure there is a service out there you can pay to generate one for you over the course of a year to make it look more geniuine. Whenever I interview someone I have a grand total of 0 time to review a github. It's just not something I can budget time for. Same goes for the hiring managers usually. They get 10 canidates in and all of them have it? Yeah they arn't spending 2 days reviewing github. I can get a much better sense of how skilled a person is working through a simple problem together.
For more Senior Positions a basic coding test (to prove that you can actually add 1+1) and several rounds of whiteboarding sessions are required.
Nahhh.why do you cringe me? why u not like Microsoft, are you one of those?
Are you asking them typical CS algo questions? Program a stack, graphs, etc etc?
I consider myself fairly proficient with Angular at this point and I've tinkered around with Vue. React I'm familiar with from a high level perspective.Anyone using angular on new projects or is the conclusion that vue and react are the weapons of choice?
Any suggestions for front end frameworks to pair up with Java/spring? Been serving it up serverside using thymeleaf as my templating engine. Seems spring jobs lean towards angular knowledge.I consider myself fairly proficient with Angular at this point and I've tinkered around with Vue. React I'm familiar with from a high level perspective.
To answer your question, it really depends on what you're doing. For simple apps Angular is an overkill. Vue is superior for small apps and multi-page apps. It's also easier to work with and understand. But if it's a large, complex app then Angular is quite nice in the respect that it comes with everything you need out of the box -- routing, http, and dependency injection. Angular also forces a particular structure on you plus you get kinda/sorta type safety with Typescript.
My personal opinion is I wouldn't bother with React unless you're trying to get a job.
I think Angular gets a lot of hate because of Typescript. But if you're a .NET or Java developer then Typescript will be very familiar.
First off, I'm a .NET guy so I'm not familiar with Java/Spring. Although it sounds like it's equivalent to ASP.NET MVC.Any suggestions for front end frameworks to pair up with Java/spring? Been serving it up serverside using thymeleaf as my templating engine. Seems spring jobs lean towards angular knowledge.
Well, if all you care about is backend then probably focusing on the web API, authentication, and database services would be best. The client-side framework doesn't really matter in that regard because no matter which you choose they will be consuming those.End goal is to get a job doing more backend architecture for large scale systems. So any other advice on that is appreciated as well. Learning node JS next. Would like to be able to walk into a situation, hear a customer's backend needs then suggest/implement the back end tech that fits their needs versus using a "golden hammer" for everything. Thought Java/spring + node would be a good start.
I hate angular with a passion, you can read my posts on this thread on that subject. React is the winner of the UI Wars, on my opinion.
and now with webhooks, it makes state management event easier.
It requires separate set of skills, for sure.All Web UI development is cancer.
Prove me wrong.
What's your opinion on GraphQL vs REST? We went REST for our Silverlight+WCF to Angular conversion and the number of end points has quickly grown out of control (plus all the authorization around each one). We began development back in '16 so there weren't real alternatives to REST. But it sounds like GraphQL may have been a better fit...but in ways it sounds like you're just moving all those endpoints deeper in, right? Rather, instead of a bajillion exposed endpoints I assume you have to parse this one query coming in to figure out which resource is being requested. Plus any filtering, sorting, blah blah blah.It requires separate set of skills, for sure.
for example
I just did this nice GraphQL endpoint on dotnet core hosted in a AWS lambda, everything from scratch.
Pretty sweet.
Yeah, but it's better than it was. The tooling has made things a lot easier.All Web UI development is cancer.
Prove me wrong.
So what your saying is I'm not wrong.Yeah, but it's better than it was. The tooling has made things a lot easier.
It's not cancer. More like really bad heartburn.So what your saying is I'm not wrong.
Thanks-
graphql = 1 endpoint and you dont have to configure all the possible query combinations.What's your opinion on GraphQL vs REST? We went REST for our Silverlight+WCF to Angular conversion and the number of end points has quickly grown out of control (plus all the authorization around each one). We began development back in '16 so there weren't real alternatives to REST. But it sounds like GraphQL may have been a better fit...but in ways it sounds like you're just moving all those endpoints deeper in, right? Rather, instead of a bajillion exposed endpoints I assume you have to parse this one query coming in to figure out which resource is being requested. Plus any filtering, sorting, blah blah blah.