I don't know if that exists, but I am looking for a minijob portal for developers.
I would like to offer mini developer tasks for money.
Does this exist ?
regards
The only one i know is freelancer.com I'm sure that many people over there would be interested in quick projects.
Or another way would be to approach developer one on one and propose those minijobs, you could pay them thru paypal for instance
Related
Looking for a list of tables that are accessible to developers to make sure we can accomplish what we're hoping to before going through all of the effort to get the data into Azure. Anything someone can share?
Adam
Xero's documentation is frustrating, as some of it is out of date and references long-dead information.
Use the Xero API Explorer to verify at
https://developer.xero.com/announcements/all-new-api-explorer
You're wise to verify this before starting coding as there are a lot of oddities (and omissions) in the API.
I am developing an application that will let users login via Twitch.
We already support Facebook login.
For Facebook, testing was easy as through a developer account I could create 2000 test accounts and signup using them one by one.
For twitch, I could not find anything similar. I am signing up everytime, verifying the email and then testing. Is there an elegant solution to this?
(I hope this won't be marked inappropriate as this is not a programming question)
Thank you.
There are no easy way to approach this,
Although Baba Tools has made a really descent tool for that, which creates temporary emails and verifies them.
I think it's the easiest approach you can get.
There are few others in the market, but babas probably the best.
Twitch does not have any api to create test accounts.
https://discuss.dev.twitch.tv/t/creating-test-users/3803
I'm having a rather general question, in the sense that I'm not even sure that it's possible. I'm trying to gather some opinions about it, coming from more experienced people.
Imagine, that I'm a member of three (just to say a number) online book stores. Over the years I have bought quite some books on all three accounts. Now, let's say I want to create an application that can login to these three accounts and do server requests to sort all my books in a single list. So that I can access my books from a single location, similar to what Pidgin or Trillian does with multiple instant messenger services.
Is that even a realistic option? Of course I dont know which server requests I would have to do and/or in which data format the data will be sent back. Assuming that this doesn't infringe every EULA out there, how would you approach this?
It's all a bit vague, but that's all I have at the moment :)
thanks a lot in advance.
I'm afraid you'll have to talk to each server via its own API (assuming it has one). You can then get the relevant info from each server and process it in your app (e.g. get the common info, aggregate it in a single list, sort...).
This is more or less what pidgin/trillian do.
IMHO the more interesting problem occurs when you want to buy a new book via your app :)
I am developing software which I want to sell online. The typical pay the vender, get a digital key that unlocks the application scenario.
I've never set this up before, does anyone have any info on good service providers, and things I need to know when setting this up?
Microsoft uses digital river, maybe check them out?
You can checkout a typical license acquisition flow using FastSpring
FastSpring / NetLicensing flow
This combines FastSpring e-Commerce and NetLicensing license management.
You did not say what language you are planning on using, but this is a great solution for a .net compiled language:
http://xheo.com/products/copy-protection
It provides two key features. First the ability to automatically generate your licenses based on many different ecommerce solutions so you don't have to keep paying a 3rd party a % for it. Second, it offers code protection to prevent people from using Reflection on your software to crack it / steal your intellectual rights. (note i said prevent, not completely stop)
I'm using FastSpring, you give them binary file and keys, and you setup your account to send an email that contains these two informations. you can tell them what you want and they will do it for you
I have a little experience with bug tracking systems such as FogBugz where help tickets are issues are (or can be) bugs, and I have some experience using a bug tracking system internally completely separate from a help center system.
My question is, in a company with an existing (home-grown) help center system where replacing it is not an option, how should a bug tracking system (probably Mantis) be integrated into the process?
Right now help tickets get put in for issues, questions, etc and they get assigned to the appropriate person (PC Tech, Help Desk staff, or if it's an application issue they can't solve in the help desk it gets assigned to a developer). A user can put a request for small modifications or fixes to an application in a help ticket and the developer it gets assigned to will make the change at some point, apply their time to that ticket, and then close the ticket when it goes to production.
We don't currently have a bug tracking system, so I'm looking into the best way to integrate one. Should we just take the help tickets and put it into the bug tracking system if it's a bug (or issue or feature request) and then close the ticket if it's not an emergency fix? We probably don't want to expose the bug tracking system to anyone else as they wouldn't know what to put in the help center system and what to put in the bug tracker... right?
Any thoughts? Suggestions? Tips? Advice? To-dos? Not to-dos? etc...
Have a promote to bug button on the help desk system, that publish the ticket on the bug tracker, with the appropiate reference info.
Is this for a production system with end users reporting bugs, or for issue resolution during QA?
If it is the former, some live person should triage the help desk tickets and only log as a bug what really is one.
If it is the latter, you should not integrate at all.
Well, it's a tradeoff.
We use separate systems for help desk tickets and for bugs.
Pros:
Workflows & requirements will probably different between devs and help desk, you can choose a system for each that fits requirements (e.g. fields that are only relevant for dev or for help desk, different kinds of email integration).
Clear responsibilities: Help desk handles tickets, devs handle Bugs.
Cons:
Integration will not be quite seamless (you need either automatic integration, which does not always exist, or manual back-forth links, which people may forget).
So far, we're quite happy with two products. It is occasionally annoying to have to paste links or close a ticket and a bug, but usually tickets and bugs are handled by different people anyway, so it's not a big deal.
One product might also work well, if you can find one which fits everyone's workflow.
In the raiseaticket help-desk system, we create a separate workflow for Prod, Dev and Bugs. The ticket is assigned to relevant group based on the nature of the issue. These tickets are not exposed to any other group. So, we can do a workaround in our help-desk portal system for the bug tracking.
For anyone in 2022 (and beyond) looking to integrate a help desk system and bug tracker, DoneDone does this well.
We use a DoneDone mailbox for general customer support (both via our support email address and the contact form on our website). It lets you have private discussion on emails, along with allowing you to assign, prioritize, tag, and create/change statuses on them (e.g. "Open", "In Progress", etc.)
We use DoneDone projects to manage internal bugs/issues/tasks.
DoneDone lets you connect support emails (the helpdesk part) to internal tasks (the bug tracking part) as well. So, if your company has distinct support and client-facing people while also having internal devs and you want to separate their work, you can create any number of subtasks from an incoming conversation.
Even if your company isn't that stratified, it's nice to be able to create bugs with their own workflows separate from a helpdesk ticket (which has its own workflow).
More info at https://www.donedone.com