russianator

Not everything needs abstraction.

FP (Functional Programming) has it's place. Sometimes a pure function is a beautiful thing to have.

It's also ok to mix OOP and FP.

Main advantage is the full sized keyboard.

If you do a lot of coding, it's just a better ride than "compressed" keyboards.

13" is a nice form factor, but I find the 14" X1 just has enough space to give a nicer typing experience.

Just my opinion, you should see if you can try one out, and see what you think.

I've had one of these and it runs Ubuntu really well.

Personally I actually prefer the IBM X1 Carbons, they have the nicest keyboard I've ever seen and a good keyboard is IMHO a must for a coder hacking keyboard.

In my opinion, you lose out where transferrable skills are concerned.

You become a platform or product expert, which can effect your career in some ways.

I've seen this in situations where products from companies such as Salesforce are concerned.

I didn't want to become a Salesforce platform expert, I wanted to be able to pick the right tool for the job, regardless, and saw heavy investment into a single platform as a disadvantage both for the organisation as well as myself and our engineers.

This is purely my opinion from the perspective of a developer/engineer who has seen my solutions removed with little understanding for the engineering and people consequences in an organisation.

The issue with nocode SaaS products is the misconception given to non technical people about what is replaceable.

Often a good business decision does not equal a good engineering decision and the management structures in place don't allow for this type of discussion to take place. This is where developers and engineers are beat out by "it's better for the business" as a decision.

Often executive managers who have moved away from technical work and are very far removed from deep (as opposed to wide) engineering knowledge, this can promote animosity between management and engineering.

Again this is purely a view/opinion from my own experience.

The organisation needs to understand: 1) What are the needs we are fulfilling 2) Are we building up engineering where we need it

When question 2 is disregarded when engineering built solutions are discarded this leads to the degredation of engineering "credit" in an organisation.

Only if you have 1,000 apps being messed with by a monkey

I would argue that there are boundaries to this sort of behaviour though.

There should be open discussion about these things.

Passive aggressive behaviour, which sounds very unprofessional.

If his manager is enabling or ignoring this behaviour, I would wager there is some toxic culture in action here.

Having said that, you should have a manager that you can give and get feedack to and from. Be open to criticism but also note any behaviour you feel is unfair or unbalanced.

If it looks like noone cares to openly discuss this behaviour I would start looking for a new job.

This is akin to Salesforce, Oracle and other certifications of their ilk.

Another vote for distowatch.

I go there from time to time when I get bored of Ubuntu :)

Rule number one, be honest.

Rule number two, don't wait to have difficult conversations, do it as soon as something arises.

Rule three, delegate organisation tasks to your team.

I still struggle with time management personally, I'd be interested in others opinions on this as well.

You will have to balance delivery over care, or going fast over doing top quality work.

Solicit feedback from your team about how you can help them.

Also, work hard to prevent burnout.

The best way to gain trust is to show you are working for your team and not for your manager.

And don't ever listen when someone suggests one on one meetings with your team members could be a waste of time.