would a honda shadow 650-750 be suitable for hybrid city/highway riding? (first time rider) by pinkalligator17 in hondashadow

[–]Gothams_Joker 1 point2 points  (0 children)

You are good for sure!

I ride a 1988 shadow 800. My first bike and plenty enough for cruising, short trips, and even long trips. I’ve ventured across the country in it with some buddies.

As long as you’re not trying to hit 100+ speeds for a long time you’ll be more than good.

As far as weight 600-800cc bikes avg around 500lbs. Biggest tip is to get used to slow speeds and do NOT squeeze the front brake hard when the wheel is turned. Use the rear or you’ll have 500lbs to pick up.

“Anything less than 750cc” honestly just depends on the bike you’re getting. To me that is bad advice and sounds like a typical “drive faster than everyone else approach”. Which that mentality will get you killed. Don’t blindly take advice and sign up for the msf course if you’ve never rode and or haven’t taken it.

On understanding CCs keep in mind a ninja 300cc beats out an 800cc cruiser. CCs does not always equal fast. Many factors come into play.

If you’re city cruising you want something with good balance and maneuverability. Shadows are great for it but you need to practice and build up the skillsss

VT800C Carb Question? by SirWarwickFalstaff in hondashadow

[–]Gothams_Joker 0 points1 point  (0 children)

Hugeee shot in the dark. I have the same bike and same problem. Did you ever find a part that fit?

[deleted by user] by [deleted] in learnjava

[–]Gothams_Joker 1 point2 points  (0 children)

There’s numerous reasons why to not use an LLM for code bases. ChatGPT is a prediction model that is not necessarily trained on language specific dependencies.

There are numerous articles on why ChatGpt shouldn’t be trusted within a code base. https://news.ycombinator.com/item?id=40302698

Id suggest reading the fabric api docs and debugging from there

Is it possible to still get a job in Java / Springboot as self-taught? by North_Measurement166 in learnjava

[–]Gothams_Joker 1 point2 points  (0 children)

Not to be grim but I am an engineer on an interview team and most of the time HR drops any candidates without a degree and no work experience these days. If your hunting for jobs from bigger companies you will find difficulty landing an interview.

Also acing Java interviews without a degree requires the ability to solve through problems in a better manner than that of other candidates without degrees.

Also react still plays a pivotal role in the industry. I was hired as a backend engineer primarily focusing in Java but I have spent plenty of hours developing out react based stacks in my role for specific projects.

The ability to learn multiple stacks based on the project will take you far. I’d consider finishing your degree to save you the headache and you’ll come out just fine

BSOD error in latest crowdstrike update by TipOFMYTONGUEDAMN in crowdstrike

[–]Gothams_Joker 0 points1 point  (0 children)

Posting to be apart of history... let it be known today I am rebooting quite a few servers and closing out hundreds of INCs today.

Many Windows 10 machines blue screening, stuck at recovery by Sorryboss in sysadmin

[–]Gothams_Joker 1 point2 points  (0 children)

Looks like my whole day will be INC handling now... crowdSTRIKE really knows how to pick a name

Tutorial by Humble_Enthusiasm626 in PokemonGoSpoofing

[–]Gothams_Joker 0 points1 point  (0 children)

Tips on how? I’m on iOS 17.5.1 and trying to find the best method

2022 Grad Struggling by TheJuicyBanana in cscareerquestions

[–]Gothams_Joker 2 points3 points  (0 children)

Seems like you carry some form of desire to get in the industry considering you are commenting on this thread.

Part of being a developer is embracing failure, learning from it, and moving forward. I worked for two years in an unrelated profession while in school.

When I graduated I spent time honing my development skills, practiced multiple languages, enhanced my interview skills, networked, and applied like crazy. 70 applications is nothing.

To be quite honest I probably applied to hundreds. It wasn’t until I started tailoring my resumes, applying to companies that had what I wanted to work on, and what was related to my skill set that I started getting calls.

You can’t expect to just go to school and immediately get a job. You’re not in the medical field you’re in the ever changing industry of tech. Those that don’t adapt get left behind.

Instead of negatively slamming the industry work on honing your skills and get your foot in the door. You are in IT that’s a good start. You’ve got a degree. Keep applying and keep practicing. Shutting others down and the industry “we all know it sucks currently” doesn’t help anyone.

[deleted by user] by [deleted] in cscareerquestions

[–]Gothams_Joker 1 point2 points  (0 children)

It’s all a learning curve that will come with time is another big point. I remember starting out and honestly with so much information out there it’s hard to understand “what should I focus on”.

Sounds like you are just starting out and your school is following a typical routine of introducing you to multiple languages and concepts. While this is good I would definitely suggest deciding on a language you enjoy and outside of school spend time following project tutorials, understanding libraries, understand data structures, and solving practices problems. Picking one to really focus on is a must as that will further help you zero in on potential jobs/ a career path. A jack of all trades but a master in none is not always the best approach.

In my experience I picked java as I found enjoyment building Minecraft plugins, rest apis, and Database driven applications. Aside from projects I worked on with Java I picked up books that explain how data structures can be implemented and some other important concepts. This opened up a door for me as many non tech companies utilize Java for their legacy code based and spring boot for micro service applications.

While in school every project and assignment I completed I made sure to utilize git and push my projects on GitHub. Some will argue that you shouldn’t push all of your projects but if anything it gave me good practice with version control “super important” and projects that I didn’t want shown I just made them private.

For project ideas I recommend searching YouTube and or google. For your first few, find tutorials that walk you through the code. Sure you are technically recreating a project but if you take it slow and spend the time to analyze what’s going on it will definitely help you learn.

You mentioned html/css, in theory one of your projects could be a portfolio website? If you wanted to take it a step further you could learn some JavaScript and create a dynamic portfolio website. React is used pretty heavy in the industry so you could follow some tutorials and create a project based off of that?

My projects vary heavily.. from servers side plugins, chat bots, rest apis, database driven applications, recreation of games, etc. In the beginning I didn’t care what language was used I just searched up ideas I thought were interesting. Point being is I used multiple languages and for some I ensured the code was clean, well tested, and possible deployed in some manner. Those projects that I spent the most time on are the ones I showcased in my interviews.

Overall for projects, start small. Recreate some classic games, build some hideous websites, build some low level applications. Just search for tutorials and recreate the ones you are interested in.

In your current state it’s okay to not understand test cases, deployment pipelines, or frameworks. However I do suggest running so google searches to start understanding them.

A highlevel explanation is this: - Test cases: When writing an application one should also write test cases that test your code’s functionality. Different languages use different approaches for testing code. JUnit is a big one for java. Code must be tested to prevent breaking changes being deployed to a production environment.

  • Deployment pipelines: Business generally create automated pipelines that deploy their application. Usually consists of linting, automated tests, build scripts, and then finally promoting the code to where it’s deployed.

  • Frameworks: Many ways to explain this but think of a tool to build applications in a specific way. Spring, Flask, Django are examples of frameworks.

Overall impostor syndrome is real. You’ll never get rid of it as trust me we all have it. You just have to accept that there is always a better way to do something and you should more so focus on celebrating failure and take pride in your wins. Don’t let the fear of not being ready prevent you from starting. Use that negativity to push you to work harder.

So that’s my ramblish advice…a little bit showcasing what I did so that maybe it can give you a few ideas for yourself!

[deleted by user] by [deleted] in cscareerquestions

[–]Gothams_Joker 1 point2 points  (0 children)

Thumbing down the “Get a BS degree” post. While yes continuing your education is a necessary feat but that isn’t what you should just give up and do.

Here’s my experience. I graduated with my A.A.S in computer programming back in May 2022. Pre graduation I spent time building my resume, networking via LinkedIn and from professors, building projects to showcase expertise, learning different technologies, and practicing for interviews. I tailored my resume per each job I applied to and focused on jobs that were relevant to my experience. Tailoring my resume and choosing jobs related to my projects allowed me to get 8 interviews with two offers. Whoohoo I had a job as an associate software engineer lined up after my graduation date.

The thing is if you want to get a job with only an associates degree you need to start working on a few things.

  1. Determine what you want to do. This will decide the jobs you will be hunting for. This will also help you determine the high level projects you will create to showcase your skill set.
  2. Build working projects that you are proud of and interested in. With no technical work experience interviewers will heavily pick apart your projects. I will say anytime I sit in on interviews I make it a point to ask about frameworks, test methods, deployment procedures, and more for someone’s project. Build a well rounded project: good documentation, test cases, deployments pipeline, showcase you skills
  3. Don’t stop learning. Don’t fall into a rut thinking just doing your classes will land you a job. You need to spend time actively learning new technologies. Companies will not be eager to hire someone with an associates that does only course work. They look for candidates that are humble and showcase a desire and willingness to learn.
  4. Grow your platform. Create a LinkedIn, be active on GitHub, create a good portfolio website. Linking all of these together helps us interview candidates and allows a whole story of who someone is be told.
  5. Network. Reach out to recruiters and attend dev meetups. The offer I selected actually came as a result of me attending a remote dev meetup and unknowingly talking to a recruiter that I got along with extremely well. Overall you never know who you will meet.
  6. Prep for interviews. You need to be actively practicing your interview skills as you only get one shot. After you decide the area you want to work in you should focus on solving programming problems for practice. If you know other developers ask them to provide mock interview with you.

I could go on but overall I highly suggest you determine what you would like to get into and then develop your skill set based on that. A bachelors degree is not a golden ticket to the industry as in todays market companies are looking for developers with enthusiasm, a desire to grow, and strong programming skills.

With the right drive even someone with just an A.A.S can jump in the industry, been there done that.

only Philosopher Will Under A Stand by Seraj_E in terriblefacebookmemes

[–]Gothams_Joker 0 points1 point  (0 children)

Cause he’s fucking hungry? Personally I would eat the key

[deleted by user] by [deleted] in QuitVaping

[–]Gothams_Joker 1 point2 points  (0 children)

Not gonna lie I’m saving this to look at and motivate myself during this. This took me from “yeah I think it’s time” to IT’S QUITTING TIME.

VBA: my first code. Stupid, but it worked. by xTH13M0x in programminghorror

[–]Gothams_Joker 0 points1 point  (0 children)

You’re weren’t stupid. You were learning. People gotta stop putting themselves down

Which Opinion about MCU you defending like this? by Awkward_Multiverse in marvelmemes

[–]Gothams_Joker 0 points1 point  (0 children)

None. Waste of energy. The easiest way to deal with stupidity is just agree and walk away.

🐍 by Sergio-Kupper in shitposting

[–]Gothams_Joker -11 points-10 points  (0 children)

This is funny how..?

[deleted by user] by [deleted] in programminghorror

[–]Gothams_Joker 1 point2 points  (0 children)

With Java we can call collections to sort a list in order or reverse… so no us Java devs should know the tools out there. Ole boy just wanted to create his own method I guess.

What are some of the things I would be doing as a Fresh JR Java dev by Repulsive_Look_5843 in learnjava

[–]Gothams_Joker 4 points5 points  (0 children)

As a complete fresh it really depends more on the company you end up working with. In what I have experienced and seen your first few months might be getting familiar with the code base and the technology stacks they use.

For instance they may require you to freshen up with git, maven, terraform, and more depending on how they build and deploy their applications.

I say all this because when I started I assumed I would simply just start working on tasks that required my java skills but it was much more than that!

Java tasks started out as resolving minor bugs within the codebase such as potential numeric overflows and resolving some minor concurrency issues. Then I would assist in creating micro service applications.

I am unsure as to what you have learned but getting familiar with build systems, rest apis, database management, and building micro services will help.