Im about to interview a breh who is asking for 120k a year salary

Silver Surfer

Veteran
Joined
May 1, 2012
Messages
37,731
Reputation
-4,741
Daps
85,018
I wouldn't say frameworks are trash. Not by a long shot. By all means, you must learn core Java as a foundation to even know what is going on behind the scenes of Spring. But once you do that, using frameworks cuts your development time dramatically. Why write boilerplate code/reinvent the wheel when you don't have to? Plus it's a necessity if you're doing any kind of enterprise development.
If I had to interview someone and he said something to the effect of "frameworks are trash" I would probably DQ him instantly.

First off its NOT necessity...especially in backend development. My guys only code in core java for our back end micro-services....its helps the apprentices learn...and it makes debugging easier because you see exactly whats wrong.

With a framework...there are layers on top of layers that will do what the core language is doing.....thats a crutch....and there are benefits...but there are cons as well

If a guy told me spring is trash and he can do better with the core...that guy is an asset and means he has a better command of the language and if necessary he can learn the framework....if a guy only know a framework then I would at him sideways
 

Silver Surfer

Veteran
Joined
May 1, 2012
Messages
37,731
Reputation
-4,741
Daps
85,018
I meant as far as learning the core. For example I can show someone who never programmed how to create a restful application with a jpa connection in spring in under an a hour and they wont have to write anything but some getters and setters. If I were to teach code I wouldn't focus on a specific language but concepts cause languages come and go. Im porting code from python to c# now cause someome quit cause he didnt wanna use NET.

bruh I can show rest call to a jdbc call in 10 minutes with core java
 

Silver Surfer

Veteran
Joined
May 1, 2012
Messages
37,731
Reputation
-4,741
Daps
85,018
you need 30 mins to download dependencies in spring:mjlol:

It also adds like 1gb of memory to a jvm

I was explaining to a director a few months ago why my team was not using spring...I said.."here is the proof...its not efficient for what we are doing...I dnt need all that overhead for something I can easily write with Java 8 libraries"
 

Maude

Superstar
Supporter
Joined
Mar 4, 2014
Messages
4,627
Reputation
3,230
Daps
19,742
Reppin
The Midwest
It also adds like 1gb of memory to a jvm

I was explaining to a director a few months ago why my team was not using spring...I said.."here is the proof...its not efficient for what we are doing...I dnt need all that overhead for something I can easily write with Java 8 libraries"
Might mention this to the lead developer during our meeting with stakeholders:mjgrin:
 

PikaDaDon

Thunderbolt Them Suckers
Joined
Oct 13, 2012
Messages
9,359
Reputation
2,334
Daps
25,321
Reppin
NULL
Not particularly fond of the copy reference deal going on here...

Code:
package com.training.example;

public class Vector2D
{

    private float _x ;
    private float _y ;

    public Vector2D()
    {

        _x = 0.0f ;
        _y = 0.0f ;
    }

    public Vector2D( Vector2D v )
    {

        this._x = v._x ;
        this._y = v._y ;
    }

    public Vector2D( float x, float y )
    {

        _x = x ;
        _y = y ;
    }

    public void setX( float x ) { _x = x ; }
    public void setY( float y ) { _y = y ; }

    public float getX() { return _x ; }
    public float getY() { return _x ; }

}

Code:
package com.training.example ;

public class Example
{

    public static void main( String[] args )
    {

        Vector2D v = new Vector2D( 9.0f, 10.4f ) ;

        Vector2D c = v ;
        c.setX( 110.0f ) ;

        System.out.println( "X: " + v.getX() ) ;
    }

}

How do I keep v's original value?
 

Kyle C. Barker

Migos VERZUZ Mahalia Jackson
Joined
Feb 5, 2015
Messages
28,280
Reputation
9,507
Daps
121,614
I wouldn't say frameworks are trash. Not by a long shot. By all means, you must learn core Java as a foundation to even know what is going on behind the scenes of Spring. But once you do that, using frameworks cuts your development time dramatically. Why write boilerplate code/reinvent the wheel when you don't have to? Plus it's a necessity if you're doing any kind of enterprise development.
If I had to interview someone and he said something to the effect of "frameworks are trash" I would probably DQ him instantly.


Same here. Those be same type of people to reinvent the wheel.
 

Kyle C. Barker

Migos VERZUZ Mahalia Jackson
Joined
Feb 5, 2015
Messages
28,280
Reputation
9,507
Daps
121,614
yep heard that too recently.....Im waiting to see how that plays out


There's always openjdk.

I think in either case if you always update to the bling term releases you should be good.


The people that will be hurt the most will be the shops that refuse to update from java 1.4
 

Kyle C. Barker

Migos VERZUZ Mahalia Jackson
Joined
Feb 5, 2015
Messages
28,280
Reputation
9,507
Daps
121,614
First off its NOT necessity...especially in backend development. My guys only code in core java for our back end micro-services....its helps the apprentices learn...and it makes debugging easier because you see exactly whats wrong.

With a framework...there are layers on top of layers that will do what the core language is doing.....thats a crutch....and there are benefits...but there are cons as well

If a guy told me spring is trash and he can do better with the core...that guy is an asset and means he has a better command of the language and if necessary he can learn the framework....if a guy only know a framework then I would at him sideways


How many oval shaped wheels have your guys manufactured?

:mjgrin:
 

Freedman

Choppers For Karate Nggas
Joined
Jun 27, 2012
Messages
18,065
Reputation
6,000
Daps
88,871
Reppin
Louisiana
Not particularly fond of the copy reference deal going on here...

Code:
package com.training.example;

public class Vector2D
{

    private float _x ;
    private float _y ;

    public Vector2D()
    {

        _x = 0.0f ;
        _y = 0.0f ;
    }

    public Vector2D( Vector2D v )
    {

        this._x = v._x ;
        this._y = v._y ;
    }

    public Vector2D( float x, float y )
    {

        _x = x ;
        _y = y ;
    }

    public void setX( float x ) { _x = x ; }
    public void setY( float y ) { _y = y ; }

    public float getX() { return _x ; }
    public float getY() { return _x ; }

}

Code:
package com.training.example ;

public class Example
{

    public static void main( String[] args )
    {

        Vector2D v = new Vector2D( 9.0f, 10.4f ) ;

        Vector2D c = v ;
        c.setX( 110.0f ) ;

        System.out.println( "X: " + v.getX() ) ;
    }

}

How do I keep v's original value?
The c.set method is changing the X value in the original object.


Vector2D c = new Vector2D ( v)
// Instead of Vector2D c = v
Should create an entire new Object with its own instance variables
 

PikaDaDon

Thunderbolt Them Suckers
Joined
Oct 13, 2012
Messages
9,359
Reputation
2,334
Daps
25,321
Reppin
NULL
The c.set method is changing the X value in the original object.


Vector2D c = new Vector2D ( v)
// Instead of Vector2D c = v
Should create an entire new Object with its own instance variables

You're right. I falsely assumed the 'Vector2D c = v' was supposed to invoke the copy constructor anyway (like in c++).
 
Top