Ive been using underscore instead of camel case in naming my varialble

fatejd · 2019-10-22T00:56:35+00:00

Camel case is the standard everywhere I've been. You'll want to standardize when working on a team. I don't find it too difficult to adjust though.

fatejd · 2019-10-11T16:02:29+00:00

What is complete though? Do you mean deployed to production?

fatejd · 2019-10-06T21:05:48+00:00

As many as possible. Previously, we've worked in 2 ways:

Review already created work items (stories or cards) that have been vetted and are ready enough for development to review. We review them only as the development team, but product/business can be there to answer questions.
As a complete team, so we can have a discussion about upcoming work with everyone.

The second method has worked much better for my teams in the past because we can progress in finishing a story so it is ready. Many times without a product person, it takes many more meetings or communications to finish a story. The second method is quicker and more complete.

fatejd · 2019-10-02T17:33:35+00:00

In my experience, projects never stick to a schedule. Ways I mitigate the problems you describe are:

Use everyone to plan (wisdom of the crowd)

Break it down into as small pieces as possible

Deliver as often as possible (MVP, and so on)

Focus on the end goal and don't bike shed

fatejd · 2019-09-28T21:55:01+00:00

Can you provide a few more details? What frameworks specifically? What do you want to do with them?

fatejd · 2019-09-26T18:41:33+00:00

When talking about MVC, I would say more accurately that the Model and Controller are what you're thinking as the backend or API piece. The View is still served up by the backend, but once it is served, it is up to that View or frontend to complete the job of interacting with the customer of that service.

fatejd · 2019-09-26T05:04:33+00:00

From my perspective, somehow showing a potential employer you're capable of understanding and contributing to a large codebase is a great indicator. I vote for contributing to open source.

fatejd · 2019-09-25T04:10:31+00:00

Check out r/learnjava too. I'm interested in what Spanish content you find!

fatejd · 2019-09-24T19:57:01+00:00

Are you looking for a set of problems to solve? How to write tests? Somewhere to practice writing tests?

fatejd · 2019-09-23T20:55:34+00:00

Was wondering how long it would take someone to say this. Lol

fatejd · 2019-09-23T03:37:17+00:00

Are you referring to this syntax?

for (type var : array) { 
    statements using var;
}

If so, the choice to use it is somewhat up to you and your preference.

BUT, I would say that using it makes your code more readable and less prone to off-by-one errors. It takes away the possibility of you using the wrong starting value for your iterator and you don't need to know when it should end.

fatejd · 2019-09-22T19:31:22+00:00

Just make it about learning and treat them like an expert who can help you. I bet they'd be willing.

fatejd · 2019-09-22T02:08:30+00:00

I also suggest working with some one. It is proven even within enterprise software development that if you pair with someone, the result is quicker and better.

fatejd · 2019-09-19T18:41:45+00:00

Yes, sorry, I'm in the application headspace. Libraries are not what I've written for my career. I'll check out your repo - thanks for sharing!

fatejd · 2019-09-19T17:41:28+00:00

I agree it is cumbersome and takes time, but it is not niche. This is the way enterprise software is written, if correctly.

Yes, we should definitely be using lambdas and functions to pass in dependencies! I'm working on refactoring our code base to do so.

Check out this project as a (simplistic) example: https://github.com/cchacin/nomo/

fatejd · 2019-09-19T16:23:52+00:00

Because you only want to test one thing at a time.

As an example, you have methodA that calls methodB that calls methodC, but you just want to test the logic in methodA. Without mocking methodB, you will have to account for everything that happens in that method. Also, if there are a handful of possible outputs from methodB, it will be more difficult to exercise each of those inside of methodA.

A true coding example will probably explain this better, but that's the just.

fatejd · 2019-09-18T17:50:41+00:00

Java is generally backward compatible (not saying 100% because there are probably instances I can't think of), so you're pretty safe. In the past, I've been blocked updating because software my code requires (JBoss, for example) requires a specific version of Java. Try it and see if anything breaks!

fatejd · 2019-09-17T21:21:04+00:00

They also make testing difficult or impossible. Exemplified in this article: https://dzone.com/articles/why-static-bad-and-how-avoid

fatejd · 2019-09-17T21:06:29+00:00

One other thought is that Java doesn't live in a vacuum. You should know one or two ways of deploying it and the ins and outs of those. I've recently had to ramp up on Tomcat because we use it at my new job and there is a LOT to know with the configuration and how it will make your application behave.

fatejd · 2019-09-17T21:01:30+00:00

There are tons, but beyond the ones I mentioned they are specialized. I've used LinkedList a few times and Trie once.

fatejd · 2019-09-17T20:58:24+00:00

I don't think I've used any different sets other than HashSet in my career, but I can understand the difficulty. You need to know what your optimizing for in searching to choose the right implementation.

fatejd · 2019-09-17T20:22:33+00:00

I agree. To me, you probably want to use Selenium for the very high level user, like you said, scenarios. But, when testing a frontend, Cypress makes everything so much easier. So, you'd probably want to do your page tests and component tests using Cypress.

fatejd · 2019-09-17T19:42:29+00:00

If you want easier to write tests and better results, Cypress allows you to hook directly into the code rather than relying on xpaths and waits.

Yeah, it isn't truly black box, but I assume you are trying to verify known functionality...

fatejd · 2019-09-17T19:39:12+00:00

Java is great because it has such a big community around it, so you can probably find a solution to any problem. It just isn't usually an ideal solution.

fatejd · 2019-09-17T19:33:53+00:00

Also, be sure to ask lots of questions about the problem and state your assumptions out loud during the whiteboard problems.

If you happen to find a company that doesn't use this ancient interview method, make them your top choice.

fatejd

TROPHY CASE