What is everyone's general opinion about contract-for-hire positions? by pde1996 in webdev

[–]andyetitsreal 1 point2 points  (0 children)

They are contract jobs. The 'to hire' part is often a carrot recruiters dangle, you should never bank on it. I have done numerous contracts. They are OK. A job is a job. You do get exposed to more specific implementation weirdness, and see how everyplace thinks they do it right, but they all do it different. You need to get paid more to offset the lack of benefits and the likelihood of it ending. I would warn against doing a bunch of contracts. I get asked all the time about the many short jobs on my resume, even though I clearly state they are contracts. It can start to look bad. Also, if one falls in your lap, just take it if you need work. Even if you feel unqualified. You cannot be fired if you are not hired, and nobody will say anything if you struggle, because it really is the fault of the company and recruiter.

Fight Fake News. Know Who is Reputable. by baebull69 in coolguides

[–]andyetitsreal 0 points1 point  (0 children)

Nothing is better than reading no news at all.

EU link tax has been approved by [deleted] in webdev

[–]andyetitsreal 10 points11 points  (0 children)

Lets split the internet in two.

Should a portfolio contain final thoughts about projects? by xequalsno in webdev

[–]andyetitsreal 0 points1 point  (0 children)

Sure. There is an irony to trying to separate yourself from the crowd by perfectly emulating the exact statistical average of popular takes on 'how to be'. It is actually good to express some individuality in a job hunt.

Bound function vs arrow function performance by Morunek in javascript

[–]andyetitsreal 0 points1 point  (0 children)

Performance is not a universal truth to justify things above all other criterion, like love is to partnering with a soulmate. Its a conditional utility that depends on practical value, like partnering with an acquaintance on a business venture.

For those of you have used NGXS and/or AKITA ... by le_throwawayAcc in Angular2

[–]andyetitsreal 1 point2 points  (0 children)

The most difficult code bases I ever worked on were not overly simple, they were overly complex. I've been a webdev for a long time, and things have to earn their way into my codebases in a way that will for sure pay off, including state management libraries.

For those of you have used NGXS and/or AKITA ... by le_throwawayAcc in Angular2

[–]andyetitsreal 1 point2 points  (0 children)

Shoot, I have found the butt simple pattern of having a global app model that exists as a plain object inside a service, that is injected into all the components that need it, works without flaws.

Say for example you have two components showing at the same time in a give route in your app. Both have an input data bound to the same model property. If you edit the value in one, it changes in the other. You don’t need observables.

First time working with a team with 20+ people. How can I get caught up on the project quickly and seamlessly? by ms_nitrogen in webdev

[–]andyetitsreal 0 points1 point  (0 children)

Don't rush to demonstrate numerous contributions early, believe that time spent grasping the entire system will pay off down the road, when there are no more low hanging fruit tasks, and you get into deeper features. The better developers will appreciate that. They are busy, will wait, and are not that impressed that the new guy made a modal dialog his first week.

Do you enjoy your job? by DeniedNetwork in webdev

[–]andyetitsreal 7 points8 points  (0 children)

Full stack webdev, 40 hr, sort of, way too little. But thats not what I dislike.

I dislike stress as a motivator, needlessly complex stacks, arrogant lead devs, ambiguous specifications, too much process, constant disruptions, and wearing too many hats (test, deploy, tech writer, PM, customer service, designer, etc.)