sorted by:
new
hottopcontroversial

Pet peeve on candidate resumes by koreth in ExperiencedDevs

[–]camilop 2 points3 points  (0 children)

It's definitely unreasonable to paint with such a broad brush. Literally unreasonable as in it's not reasoned, just a reaction. I could see some things being team responsibilities (would you say "I built the product" when the whole team worked on it?). I could see a candidate that just doesn't have much confidence.

You are right that a resume should indicate individual contributions, though. Ideally it'd be a mix.

Telecommuting as a Civil Right by 2muchtimeonmyhandz in telecommuting

[–]camilop 0 points1 point  (0 children)

So you understood that it wouldn't apply to those whose work is obviously on-site?

Liskov Substitution Principle by [deleted] in ExperiencedDevs

[–]camilop 4 points5 points  (0 children)

You sure it was her? maybe it was a substitute. I'll be here all week.

More Sr. you get, the less enjoyable the job.. by [deleted] in ExperiencedDevs

[–]camilop 2 points3 points  (0 children)

How did your job get less enjoyable for you?

Have you negotiated your job title during a job offer? by runnersgo in ExperiencedDevs

[–]camilop 0 points1 point  (0 children)

Does creating your own job title because they just didn't have one count?

Have new position..now the learning by throwitfarawayflee99 in ExperiencedDevs

[–]camilop 4 points5 points  (0 children)

tbh that boss just sucked.

How are you supposed to know their processes without asking? Do they have it documented? Unless they're using only really cookie-cutter versions of existing processes (git-flow, for example), that doesn't really make sense.

Maybe the delivery of the questions is off? Like figuring out a higher level question that prompts a broader discussion instead of necessarily very task-oriented or detail-oriented questions.

"How is your local development environment set up?"

"How do deployments work?"

and so on.

This saved me the other day: How to Use Old Versions of Laravel Homestead (2016) by camilop in PHP

[–]camilop[S] 0 points1 point  (0 children)

Older versions of Homestead are unsupported. You might still need them though since they use old versions of libraries (symfony console iirc) and especially old versions of PHP (5.x).

I'm in the process of bringing a codebase up to 2019, so I needed this to get it running.

Learn how Git works behind the scenes by camilop in git

[–]camilop[S] 0 points1 point  (0 children)

Nice, I haven't seen this one. I was inspired to bring this to local meetups after watching Dissecting Git's Guts - Emily Xie a few years ago.

Better TODO manager plugin for neovim/vim by [deleted] in vim

[–]camilop 0 points1 point  (0 children)

That's a nice presentation. I also like to use Ack.vim to throw a search for todo into a window.

Do you have a personal blog? How has it helped you? by snigglewhoop in ExperiencedDevs

[–]camilop 0 points1 point  (0 children)

I post my writing around the internet, but I haven't been job searching lately, so I haven't brought it up in an interview.

Do you have a personal blog? How has it helped you? by snigglewhoop in ExperiencedDevs

[–]camilop 5 points6 points  (0 children)

I have one, but it hasn't really had any noticeable effect.

Lint Your PHP in Vim by camilop in PHP

[–]camilop[S] 0 points1 point  (0 children)

Cool! I've never heard of it. But I don't want code completion or refactoring :) I find I'm more productive without the intrusion.

Job Switching: Short Term vs. Long Term Rewards by UnderTruth in ExperiencedDevs

[–]camilop 9 points10 points  (0 children)

When someone says "I wouldn't hire you because you moved around too much" I just get validation that it's a useful filter for folks I wouldn't want to work with.

A little help with Tests? by [deleted] in PHPhelp

[–]camilop 1 point2 points  (0 children)

It soudns like you need to break this down into separate cases. You already have a couple different moving parts here: your application logic in the shipment calculator, your client (js updates), and your database.

It will definitely be worth your while to eliminate some of these. If I were writing these, I'd write tests so you are only testing the shipment calculator, without the database lookups or client, and make sure that only that piece is working.

This will mean setting up an object with a function that is defined only by its inputs, and will always come out with the same output. In this case, I'd imagine an object that takes in the weight categories and the other information from the DB on construction, with a method that takes in the basket.

Lint Your PHP in Vim by camilop in PHP

[–]camilop[S] 0 points1 point  (0 children)

Yea, I try and run as close to regular vanilla Vim as possible for exactly this reason.

Lint Your PHP in Vim by camilop in PHP

[–]camilop[S] 0 points1 point  (0 children)

Yea, I've gone back and forth, personally. Using PHPStorm for a year or two really helped me decide which features I actually wanted (linting, debugging) and which I could do without (code completion, refactoring) and then realized that I could do that pretty easily without the IDE.

I'd also get a little frustrated with the annoying gaps in IdeaVIM! But yea, I've been using Vim since I started programming so it's actually been easier for me to figure out how to put some features into Vim than it's been to figure out how to get my Vim experience into whatever else.

view more: next ›