paul nisset

Thank you Heather . Good luck with the book.

You lie.

I have been guilty of that and it worked out. That's how I got my first job .

Tech recruiters and HR departments are indeed pretty clueless for the most part.
Some get it but most do not. They just want to check boxes.

The thing with relational databases kills me. They really are all the same. Just some different bells and whistles .

Hi,
I'd like your insight into  an issue that has come up repeatedly in my career when I tried to switch technologies that I was using.
Recruiters  only respond to resumes that have a significant relevant professional experience in a language or technology that is required for  a particular  job.

For example : I might know Python well but not used it at a previous job or used it in a limited capacity. I see a Python based job that I can do.
How do I break through the recruiter/hiring manager wall than says I am not a Python programmer and my resume is cast aside?

Thank you,
Paul

Thanks Venkat .
That a good suggestion. Familiarity is a temptation . I've also seen in it the code of people I've worked with.
ie. A new project but coding style is  15 years old.

Hi ,
I'm sure this is covered in your book but was wondering what you consider the biggest advantage of using the streams API over the collections API for handling data ?

A sample use case:
You want to iterate through a list of email addresses . If the the email is in a second list , you  send an email then handle a bounced email or do further processing after the mail is sent if not bounced.

For me, it would make more sense to use an iterator for that.

thanks,
Paul

creativity in itself is a skill that can be learned and practiced.

That's a great point.
Thank you for pointing out  the distinction.

That's an interesting example of exercises to do. Thank you for the tips.

I totally agree with both of those points . Nothing quite replaces actually programming and trying to make something work. Especially when I don't l know how to  do it. Those situations inevitably involve a lot of reading as well.

Hi Wouter,
I agree with  you about quick fixes . You might resolve an immediate problem but they usually don't make you better as a programmer  . Other than reducing the stress of the immediate problem, of course !

I tend to take a process approach to projects .  I can see how thinking creatively would be an important part of that process.

This seems like an interesting book.
thank you,
Paul

Hi,
I like it when I get advice that involves concrete actions that I can take.

The Amazon bullet points of the book mentions "Actionable advice and thinking exercises that will make you a better programmer" .
Can you describe what you think is the most important exercise that programmers should do to become better ?

Thank you,
Paul

My frustration with IntelliJ is with the amount of configuration you have to dig through to cut out the intrusive suggestions, hints, etc... I have spent a half hour or more to just turn off some intrusive feature or other . It kills the joy of just getting on with actual programming. The tip on Reveal sounds useful.
The Android tooling is only reason I use IntelliJ .
thanks.
Paul

"... it seems that many JVM languages besides Java, like Scala and Kotlin, concentrate on IntelliJ support and mostly ignore Eclipse users."

That is completely the case in the Android world. Google has forced users to basically use IntelliJ as the development environment. Technically you can use Eclipse but it is a royal pain . Google has clearly embarked on a strategy of forcing devs to use Kotlin in an IntelliJ environment. I personally think IntelliJ is an over engineered and intrusive piece of garbage.  Google's approach has really turned me off Android development. Google wishes it was Apple and had a completely closed environment for devs. ( Xcode and Swift).

Hi Stephen ,
It approximates my process to some extent especially working  with an existing code base. My main goal with an existing application is to not break what is there and abstract out new features .

I do a lot of middle tier development in Java as well and my process there is usually : design ,write unit tests ,then code .
The unit tests make my intention clear . If the feature works on it's own ,it's going to be more resilient and less likely to have adverse effects on other code.

It would be interesting to see this from a PL/SQL perspective.
Paul

Hi Stephen,
Thank you for providing more context to the book.

I just finished  a job where I was the sole person maintaining a website that used PL/SQL on the backend.

I generally left the implementation details out of the discussion with business users/stake holders when it came to new features. When it came to modifying features, I might have to to go into the implementation details on high level for explanations or limitations  on what was currently there and what was possible.

Good luck with the book.
Paul

Hi ,
I read the Amazon description of the book. It says because many databases are being pushed to the cloud ,the book is for dev ops engineers ,architects ,and sys admins but the bullet points seem targeted more at developers .

Is there a difference at the PL/SQL level and the code that gets written between an on premise instance and cloud instance of an Oracle Database ?

thank you,
Paul