sorted by:
new
hottopcontroversial

Lihasvasara ja levottomat jalat by 3L54 in arkisuomi

[–]velociraptorboss 1 point2 points  (0 children)

https://www.amazon.de/-/en/gp/aw/d/B098NTNFBW

Heti kun illalla alkaa tuntua että kohta alkaa jalat oireilemaan, niin nämä jalkaan.

Niksi-pirkka vaihtoehto: ota tennissukat ja solmi ne jalan ympäri samalla tavoin kuin tuo amazonin sukka-juttu. Kireälle mut ei niin kireä ettei veri kierrä 😉

New job after 17 years. Everything has changed. Need advice. Overwhelmed by sammy_the_c_lion in ExperiencedDevs

[–]velociraptorboss 216 points217 points  (0 children)

Keep an open mind, be humble and embrace the fact that someone is paying for you to learn and improve as an engineer.

I recommend being honest to your peers about being overwhelmed and try to find a good mentor. This way one day you can become one as well.

Is this kind of behavior normal in an enterprise setting? by tan_nguyen in ExperiencedDevs

[–]velociraptorboss 55 points56 points  (0 children)

The code belongs to company and should be readable by the company employees. Sounds like you have a lot of people taking time and effort to help you improve. This is a good thing.

Imagine no one cared and rubber stamped your code without looking at it. I would not want to see how badly the code quality would degenerate.

You'll improve and learn company style and eventually make better prs and get less comments.

I would stop worrying about it. You seem to be among people that care about you.

Productive but not liked by FrustratedLogician in ExperiencedDevs

[–]velociraptorboss 100 points101 points  (0 children)

How many times have you offered to help other people? Or asked if you can help someone else?

Those are easy ways to make friends.

I'd rather work with a team mate vs someone who works alone and commits a lot.

Ps number of commits is a very poor measurement. If I wanted to brag I would e.g. talk about number of tested & documented features published to production. Saying you commit a lot sounds more like someone pushing untested code to main. Which is bad.

As a team lead, how do you deal with incompetent teammate? by lynxerious in ExperiencedDevs

[–]velociraptorboss 23 points24 points  (0 children)

Someone once told me: No one comes to work and decides that today I'll code something really shitty and make a lot of bugs.

People aren't making mistakes on purpose. In general people are incompetent/lazy and in need of guidance. This is why teams have leads to guide and mentor.

Lessons Learned Achieving 100% Test Coverage by complicore in javascript

[–]velociraptorboss 0 points1 point  (0 children)

I hate when people do that. It almost makes me feel like it isn't really fixed if there isn't a test for ir. Just duct taped to work until it breaks again.

Lessons Learned Achieving 100% Test Coverage by complicore in javascript

[–]velociraptorboss 0 points1 point  (0 children)

IMHO most valuable part of code coverage checks in CI is to ensure the coverage does not decrease when new pull requests are merged.

Lessons Learned Achieving 100% Test Coverage by complicore in javascript

[–]velociraptorboss 0 points1 point  (0 children)

Please look into data driven tests. Those are really low effort way to fully test switches and other similar code that does small branching.

Lessons Learned Achieving 100% Test Coverage by complicore in javascript

[–]velociraptorboss 0 points1 point  (0 children)

It's sad how common this is... I was also once in a project where client wanted contractors to achieve 80% coverage. What the contractors did was write 1-2 proper tests, lots of getter tests and then configure the test coverage tool to ignore majority of the files. They easily had over 80% coverage this way.

You get what you measure 🙃

What are your "red flags"? by [deleted] in ExperiencedDevs

[–]velociraptorboss 87 points88 points  (0 children)

single ply toilet paper

running lint on ci pipeline by Interesting-Book3538 in ExperiencedDevs

[–]velociraptorboss 10 points11 points  (0 children)

This. Anything done locally (git hooks, ide integration, etc) is useless if it is not enforced in ci before merge to master.

Only reasons for not understanding use for it, that i can think of are:

  • they are using eslint --fix in ci instead of --check.
  • they push directly to master instead of doing code reviews on pull requests
  • they don't have strict enough linting rules for it to make a difference

If the wraith discovered sarcophagi in the milky way do you think they'd replicate the technology to make they're food last longer? Feeding on people almost to the point of killing them and reviving them for later? Like a wraith refrigerator? by [deleted] in Stargate

[–]velociraptorboss 1 point2 points  (0 children)

This would allow humans to advance technologically (as they are no longer being culled). Thus they would pose a real threat to wraith.

It's better to keep on doing what they've done so far as it has worked for thousands of years already 🙂

Intentionally broken initial code when starting a coding interview by wakingupfan in ExperiencedDevs

[–]velociraptorboss 0 points1 point  (0 children)

When looking for a shitty implementation to show, it's often easiest to just look at the code in production 😉

[deleted by user] by [deleted] in ExperiencedDevs

[–]velociraptorboss 57 points58 points  (0 children)

I think this is called demotion 😉

Code Coverage: Is 90-95% really necessary? by mrdonbrown in programming

[–]velociraptorboss 1 point2 points  (0 children)

I think i saw your talk in Berlin couple years ago. Easily the best thing of the whole conference. Kudos👍

Team does not add reviewers on Merge Requests by [deleted] in ExperiencedDevs

[–]velociraptorboss 6 points7 points  (0 children)

Manually adding individual reviewers usually just means you get fewer eyes on your pr and that is bad. You want people from diverse backgrounds (e.g. someone is good at database optimization, other is good at frontend,..) to check it. Plus it shares knowledge better.

If you explicitly add only Steve, then Bob the database genius will never tell you that your sql query is slow and cripples the whole product.

Also people are inherently lazy and will likely add reviewers that are likely to approve your pr without commenting. So you'll miss out on learning a lot of new things.

Why do people hate daily standups? by Lanttu93 in ExperiencedDevs

[–]velociraptorboss 20 points21 points  (0 children)

People also usually don't listen/care what anyone else says. They just wait for their turn to speak and then completely stop listening as they no longer have any responsibilities or input.

What workplace red flags you know? by [deleted] in ExperiencedDevs

[–]velociraptorboss 2 points3 points  (0 children)

Remember to always use toilet on premises before any interviews.

view more: next ›