Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "task scheduling"
-
Project Manager: Hey Gid, we need to start migrating project-A to the new Server.
Me: Okay, I will inform Dev-Q.
Project Manager: Please do and treat as top priority!
Me: Hey Dev-Q, we need to migrate project-A to the new Server and we need to get it done asap.
Dev-Q: But I'm currently working on some critical bug XYZ which PM wants fixed before COB.
Me: I dunno maybe you want to speak with him.
Dev-Q: I was told to...
Project Manager: Yes! we need that done right away.
Dev-Q: What about the critical...
Project Manager: No! treat this as top priority the client just called.
Dev-Q: Okay.
Me: Any update yet?
Dev-Q: Yep but it seems like the database is quite large and the migration may take a while.
Me: Okay take your time.
Dev-Q: {hours later} Pheww done! All files and database migrated successfully.
Project Manager: Good good. So the critical bug XYZ was also completed and migrated to the new server right?
Dev-Q:5 -
WHY DO WE HAVE TO BUY THE PROFESSOR'S BOOK JUST TO BE ABLE TO PASS THE COURSE?
It's so stupid, I'm currently attending a Operating Systems course at university and the professor NEEDS us to buy his book because all of the tasks and seminars are based on his book. It is stupid! There are thousands of books out there on Operating Systems programming! Free ones too! But instead we have to spend 800SEK (100USD) on his book.
And guess what? There is literally one task based on his book... To summarize the chapters about Fixed Priority scheduling and Dynamic Priority scheduling. Which is 15 pages out of 200+.
All the students attending the course are going to the director of studies and complaining next week. This is unacceptable. If it was a good book, sure. But the book has the same exact information as multiple free e-books we've found.
Ridiculous.15 -
Whatever you do, don't do this.
- a sleep for 300s to avoid full 24 hour rollover (lol)
- sleep 1d instead of cron; so at random times emails will be sent out or they won't at all
- this is a laravel project, there's a thing called task scheduling: https://laravel.com/docs/5.8/...
Git blame: https://github.com/invoiceninja/...
The actual core project docs at least tell you to setup a cron, though not via * * * * * nor task scheduling, which isn't as much of an issue though as their dogshit docker compose: https://invoice-ninja.readthedocs.io/...6 -
Had a technical interview with AWS on Wednesday. Woke up Thursday with the flu. Thanks, body, good to know the long tradition of sickness following completion of highly anticipated task is alive and well. Had to reschedule interviews and hold off on scheduling other interviews. (Damn it!)
To protect my repos from my brain on brain fog, anything I’ve done the past few days have been on branches titled “fever” or some variant thereof (“fever1”, “fever2” when there were two approaches I was trying).2 -
I recently have been delegated the responsibility of managing a 4 people team by planning the sprints, scheduling tasks, and in general "take charge" (as said by the boss).
What bothers me is there is this "developer" with a heavily toxic attitude, who feels he is above all laws and knows everything just because he joined some months ago all of us.
He is basically a human linter. When he code reviews, you can get away with any major mistake if your linting and indentation (and all that shit) is according to "his standards".
A new guy recently joined the team and was given an overwhelming task by the boss just to test whether he belongs here. (Again, wrong, in my opinion). He didn't know any of the technologies he needs to work on to complete that task but he still learnt them and got a working product. Albeit not according to our God's "standards".
Cut to the chase, the asshole dev is now mocking him in PR comments and demeaning him in every discussion. As a "team lead", what should I do? If I let it go, it'll make the environment toxic and I don't want him to get away with it. If I do take any action, I don't want to be seen as as pussy who can't take such minor insults. Please advise.
PS. The asshole developer once wrote a "friend request accept" API endpoint in such a way that when any single person accepts a request, that'll cause all pending requests (from any person to any person) get accepted. Fucked up the DB queries basically. This is just to give a perspective on what I'm dealing with here.4 -
So I just got asked for a quote for developing an app for a client's friend. He wanted an app that requires me to build let's just say a combination of what you see on uber with the live tracking of your uber driver, seeing all cars around your location and determining the closest one (It wasn't necessarily cars) plus profiles and another app for another set of users (I can easily make this one and determine the logged in user and in turn tailor the features for that user but they wanted two). An admin portal also was included and I had to do various integrations with Google maps. In app purchases was also necessary. Logs as the app has to keep track of all activities basically. A wallet feature was also to be implemented, scheduling, rating and complains section was also something requested and finally a mini accounting system was also to be developed. I was going to do this singlehandly as a freelancer. Obviously this is a lot of work. I also gave them a timeline of about 3 months for development. Which meant I was going to be putting all my time into developing this. Front end and backend for the app and front-end and backend for the server and database architecture. I charged them $10,000 not only for the work but also because they were going to be making money off of the app. They go "wow and why does it cost so much"...Judging from their reactions I don't think they will move further with this with me because of costs...😂 I can't even begin to wonder why they think that isn't a fair price. I have learnt from previous work before that you always state a cost for which you are absolutely sure you would want to work for else you would start doing the work and once you see how little you are being paid for so much work you end up hating the work and completing it ends up being a difficult task.10
-
I am working on a task given to me by a huge company to test my skill.
I am applying for a junior position.
I am doing it by myself of course but I googled a bit and the problem is called job shop scheduling or multiprocessor scheduling (not sure which one it actually is).
The topic is a bit altered (logistics) but it stil is the same problem.
I am really close to the solution.
The testcases they provided all work but I came up with some that don't.
Do you think this problem is appropiate for a junior (either of those)?