Joined devRant on 4/3/2016
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
any example of what would be a config in their mind?
Were they thinking about something like a CMS where non-tech people could edit pages?
Or were they thinking about something like featureToggles to disable existing functionality?
Used to feel sad about how accurate this is.
But I realised - it's the same for designers I bet.
Show someone an entire page design and they go "looks nice"
Show a single heading and they go "the letter spacing could be better, the margins don't align and this color is too close to another color"
Consumables are always good gifts - even if you already own the same thing you can still use more.
Wine is the default gift for house parties for a reason.
And if you get something you don't like you can re-gift it the next time you go to a party.
I'd be happy to get some expensive coffee.
Fits well with the dev theme too 😬
I would avoid purchasing items as because it's no fun if the award is $100 headphones when you already own $150 headphones. Or if you wanted on-ears but the price was over-ears. Just leaves people thinking "wish they let me pick what I wanted"
Gift cards are great.
But on the positive side : you got to the final interview! You passed the tech interview.
That means you're good and absolutely a fit!
I know it feels like shit to get turned down but sometimes it's just bad luck and you would've got the job if they hadn't found someone who had 1% more experience.
"They should just tell me 1 day after "
That's a big expectation.
Saying no to someone that far down the process is a big decision for the company.
might take time to get everyone together cause you might wanna disscuss and get second opinions from devs etc.
Sometimes people disagree on if the candidate is a good fit that leads to extra time before making a decision.
Sometimes candidate A might be okay but they need to await candidate B to see if they are even better.
The interviewers might alsonhave lots of other work meetings after the interview so its hard to find the time to properly evaluate someone fast.
And when they finally decide to say No, people write down some words about why they didn't get the job, and perhaps some feedback. To avoid just giving a Blunt No.
(Yes I know that might be silly as some candidates just wanna know ASAP if they should move on or not. But some are crushed when told No if they don't get why)
Maybe you were one of multiple candidates in a close competition for the same job- so they had to up the game to be able to decide which one of you to pick.
Why aren't you a writer for Dilbert?
This along with the "turning the manager on and off again " as the punchline would be a perfect comic strip.
Damn, That meme never fails to make me laugh. One of the most reusable ones.
On the bright side: I'd call that a quickly caught and resolved issue - and it's neat that your org allows you take time to fix stuff immediately rather than ship bugs because the new features in the sprint are "too urgent to be delayed"
How do these Pro bono programs work? How long will you be there for? Is there a stage where you get to evaluate your experience?
I set squash as the default option in for the repo in github.
Sure you can bypass it if you do manual merges but that gets rid of MOST problems.
With the ability to patch games this classic quote from Shigeru Miyamoto has become obsolete
"A delayed game is eventually good, but a rushed game is forever bad."
It's now only applicable to non-patchable games like cartridges.
Does the manager really just go around asking devs about how to save money?
Devs usually don't even look at the budget for anything other than licences. Not like we know how much the marketing department costs.
Cool. Love Knights and Merchants. But sounds very complex to do as a side project.
I used to write fun quirky test strings and debug messages with curse words... Until a colleague pushed a similar message to prod and it became a huge deal at the company of how test values should always be harmless stuff.
I can only say: keep at it! Try a few different companies and see if you still feel the same way.
When I started developing I sometimes felt like it was not a meaningful job: I had dreams of doing ”important work” like education, law, health care.
But after a while (it didn’t come right away) I started to enjoy problem solving. It didn’t have to have deep meaning - I enjoyed the task itself - kinda like how I enjoy playing puzzle games.
Then after a while I got good at it.
And then I started to feel like ”Hey, I can really get things done with software. Wht should I work in healthcare - other people are better at that. The place where I can make more of a difference is: software”
I also started feeling less stress about being assigned to projects with bad tech. Cause then you can often make big improvements, which is fun. With a perfect project there’s not as much obvious stuff to improve. 😁
I like the design and there’s tons of good content. Most stuff I read there is well written, short and to the point.
But the biggest advantage of being on there is that it’s easy for readers to discover new content. And they have good SEO - I often find medium articles when googling for a topic such as opinions on CSS preprocessors
I should give it another try.
Tried it many times in the past but end up disabling the timer when I'm in the zone and really don't feel like I benefit from taking a break, and forgetting about enabling it again.
But I do feel like I could use it whenever I'm stuck on a problem and getting nowhere.
@aviophile I doubt you'll need to guard against revenge reviews. Not many people would lash out against a headhunter for not getting you a job.
I actually think the opposite. People would be scared to dish out bad reviews.
I feel the opposite. About all your bullet points.
Now I'm curious : did it go unnoticed just cause all people only tested on similar devices?
So the issue was only super noticeable on exotic devices which no one in the team ever used?
To give these idiots the benefit of the doubt
What they call "hack" might just be taking a screenshot or modifying the site locally in devtools or something, and show it off to their friends to try to troll them.
So a bunch of text was just Times New Roman or whatever is that user's browser default?
Also maybe to make sure passwords can be emailed while avoiding potential unicode issues in email clients
@N00bPancakes a lazy way to prevent SQL injection and negate risk at the expense of the user
If the idea is along the line I imagined :
Might not be necessary to have a fixed set of criteria but rather just a textbox where you can wrote whatever you want.
If I was to post a review I might just wanna say one specific thing like "They don't know they java is different from js" but I don't know about anything else.
Or "communication went smoothly" but I don't know their tech skills.
However I think if you open it up to user reviews you should have a field for specificity the nature of how you met the recruiter: how many interactions, just email or phone, etc
Pretty good idea. I would use that to look up recruiters who email me and contact me on LinkedIn
Trying to script some event in Adventure Game Studio
I don't know angular tests but for tests in general I really recommend setting up a debugger!
It's useful to be able to step from the running test into your actual code. Even if the error gives you a stack trace - sometimes you really need to step to realise the flow.
Quite often you notice some function got a strange parameter due to a bad mocked test data or not doing cleanup after previous test.