I have just going through https://visualstudio.microsoft.com/vs/pricing/ and found the prices to be 45 $/ month or 1199 $/year for Professional subscription. Is this cost per user? if so, do I need to purchase 100 subscriptions (4500 $ / per month!) for 100 developers in my company?
It's per user. It's better described on the following page:
https://visualstudio.microsoft.com/vs/pricing-details/
I'm just looking for the same and you can be glad to have a price tag of $1199 - to me as single user located in Germany this turns into 1540€ on check-out, that would be $1813. VAT is only a small share of that difference.
Btw, the fee is for the first year, renewal will be relatively cheaper.
With your larger number of seats, you should also investigate the SKU 77D-00092 and 77D-00095 respectively. As I see them advertised in various places these still come with two years of MSDN subscription rather than the one year offered on the MS web site, also at a lower price. Maybe they are missing bundled Azure credits? Those SKUs appear to require an "Open License" plan with at least 5 seats - that's as far as I got.
Related
Does google have an API for this feature?
https://www.google.com/search?q=product+manager+jobs&oq=product+manager+jobs+&aqs=chrome..69i57j0l4j69i60l3.5823j1j7&sourceid=chrome&ie=UTF-8&ibp=htl;jobs&sa=X&ved=2ahUKEwjPuIDJhebnAhWTqp4KHTXeCB0QiYsCKAB6BAgGEAM#htivrt=jobs&htidocid=2YjfCdSoJeXy_7nXAAAAAA%3D%3D&fpstate=tldetail
Wherein in the API I can pass a keyword then returns open jobs related to the keyword.
Right now google does not have such API, they only have an API for a job to be indexed and appear as a result. If you want to get jobs results you can use third party solutions for it.
I work at SerpApi and we have an API for Google Jobs.
You can check the playground and documentation to get a better idea of how it works.
Here is a part of a response sample for an individual job listing:
"title": "Staff Product Manager",
"company_name": "BuzzFeed",
"location": "New York, NY",
"via": "via Greenhouse.io",
"description": "The Role\n\nWe’re looking for an experienced product manager who is eager to help us drive retention and loyalty across our core BuzzFeed Products. You’ll be the product lead on a cross-functional team of engineers, designers, and data scientists that are focused on creating a differentiated and compelling site experience that our community of users will love.\n\nWhat You'll Do\n• Develop a strategy for driving retention and loyalty across our products by working with your other team leads and partners throughout the entire organization\n• Your purview over the core site experience would span BuzzFeed.com as well as our Google AMP, Facebook Instant Articles, and Apple News pages.\n• You would closely collaborate with our app team with the potential (but not requirement) to also manage an additional product manager\n• You would be responsible for thinking through how people are interacting with and coming to our various pages and empowered to create a strategy for the best way to drive... retention and a deeper level of engagement\n• You would be expected to help set the team strategy, prioritize the team’s work, write OKRs for individual products or projects, and communicate and coordinate the team’s plans with stakeholders within and outside of Tech\n\nYou Are\n• Experienced: You have hands-on experience launching and managing digital products, with a slant towards a consumer experience and how that drives the business and 5+ years of product management experience\n• Collaborative and communicative: You have a demonstrated ability to work well and communicate with engineers, designers, and data scientists -- experience working with business and editorial stakeholders is a plus\n• Curious, analytical, and proactive: You don’t merely accept outliers in data, but actively investigate and dive into the numbers and research to find novel insights and new product ideas\n• Comfortable in the spotlight: You will need to collaborate with and help influence senior leaders across the company to advance the team’s vision and product strategy in a fairly complex problem space\n\nA few examples of current team projects\n• Launching a new user profile experience\n• Creating new ways to reward engagement and establish habitual user behavior\n• Improving our notifications system\n• Improvements to the quiz taking experience\n• Creating ways to subscribe to topics to improve and personalize the site experience\n\nAbout BuzzFeed Tech\n\nBuzzFeed Tech is a group of about 150 product managers, engineers, data scientists, and designers that are focused on building great products and content experiences that bring our audience joy and truth. We’re a collaborative and friendly bunch that works in a typical agile way with sprints, JIRA, OKRs, and a close working relationship with management.\n\nLife at BuzzFeed\n\nAt BuzzFeed, we believe our work benefits from the diverse perspectives of our employees. As such, BuzzFeed celebrates inclusion and is committed to equal opportunity employment. At BuzzFeed, you can expect:\n• A supportive, inclusive atmosphere on a team that values your contributions\n• Opportunities for personal and professional growth via work experience, offerings from our in-house Learning # BuzzFeed team, our Employee Resource Groups, and more\n• An attractive and equitable compensation package, including salary and stock options\n• A generous and well-rounded benefits program featuring PTO, unlimited sick time, comprehensive medical benefits, a family leave policy, access to mental health platforms, retirement plans, gym and wellness discounts, and much more\n• Plenty of snacks (healthy and indulgent), catered lunches, beverages, etc..\n\nBuzzFeed is the world’s leading tech-powered media company, with a cross-platform news and entertainment network that reaches hundreds of millions of people globally. The company aims to spread truth and joy across the internet by producing articles, lists, quizzes, videos, original series; lifestyle content through brands including Tasty, the world’s largest social food network; original reporting and investigative journalism through BuzzFeed News; strategic partnerships, licensing and product development through BuzzFeed Marketing; and original productions across broadcast, cable, SVOD, film and digital platforms for BuzzFeed Studios.\n\nBuzzFeed is proud to be an equal opportunity workplace. All qualified applicants will receive consideration for employment without regard to, and will not be discriminated against based on age, race, gender, color, religion, national origin, sexual orientation, gender identity, veteran status, disability or any other protected category",
"extensions": [
"Over 1 month ago",
"Full-time"
]
},
How do I create a module for partial payments ?.. means like client can pay Full or "50% now and 50% later". He should have the option at the time of checkout. Invoice will be created for the full amount but payment only 50%
How do i do that?
it should be possible and there is more than one way to do it.
I can suggest you the following solution for instance:
In case you are using a payment provider, you should modify its module in some way in order to take in account the 50% payment. For instance, an extra payment option should be created.
The remaining 50% should be persisted along with the order (custom order attribute)
However, keep in mind that in Magento, an order can only have 1 payment method.
Magento doesn't do this out of the box.Implementing this is a lot of work, because you have to pay attention to a lot of things.For this one I would advice to look at the already existing extensions. First of all because since it's such a tricky thing to build yourself better get something that has been proven to work and second because they're not that expensive. Probably the hours you'll spent on building itself won't weigh up to the cost of the extension.
Milople offer an extension for this where it is possible to pay Full or "50% now and 50% later".
i have an issue with the feed that is sent to my google merchant account (order_shipments.txt) there is 4 columns
merchant order id
tracking number
carrier code
other carrier name
ship date
i have set my shipping as FREE SHIPPING with the shipping magento method for Free Shipping, the problem is that under my feed all the tracking numbers shows as carrier (other) and i need under my feed on carrier either UPS or USPS. because every time we ship an order we enter the tracking number and the carrier for the shipment. any suggestion will be highly appreciate.
Hopefully I'm not too late!
We just patched this exact issue (as well as others) and have documented the necessary modifications at http://www.dcjcooltools.com/blog/magento-extensions/the-nightmare-that-is-google-trusted-stores-for-magento/
Look for the post in the comments that discusses carrier names. We are looking to create a patch extension so that you don't have to modify core Trusted Stores files.
Let me know if this solution works for you!
Regards,
Evan
in our website www.theprinterdepo.com we are going to implement google checkout. However I am not sure in what shipping methods or strategy to use.
In this page:
https://developers.google.com/checkout/developer/Google_Checkout_XML_API_Carrier_Calculated_Shipping#Process
Google says that they calculate based on the total weight of the items, but the thing is if one person buys one printer thats fine, but if he orders 3 printers of 50lbs, the shipping cost is invalid calculating it with 150lbs. It has to be calculated as 3 packages of 50lbs.
How would you do it in this scenario??
I have only had minimal investigation to this, but I don't think this can be handled by default installation. I know that you would need a shipping extension that can support the Google API shipping-packages, but real issue is that not even the Google API can support more than one package, either by API limitation or restriction by choice.
The <shipping-packages> tag encapsulates information about
all of the packages that will be shipped to the buyer.
At this time, merchants may only specify one package per order
I would love to see this come to full use as it would be a great addition to be able to say that anything with a weight over x requires additional packaging but currently I don't think it is possible. While this can be accomplished by separating the order into three orders, but that will over complicate the user experience and possible cause loss of sales.
Source:
https://developers.google.com/checkout/developer/Google_Checkout_XML_API_Carrier_Calculated_Shipping#tag_shipping-packages
The "limitation" mentioned above is only if you will rely on Google to calculate shipping for you using what they call carrier-calculated-shipping.
You do have other options to calculate shipping:
you can pre-calculate using whatever formula (or shipping service/plugin) you have based on the cart contents (you would know this prior to handing off the cart to Google for Checkout), which is essentially sending a flat rate shipping cost to Google, or perhaps;
use the merchant-calculations-api option so you can account for the destination/delivery address (not just cart contents). This option is more complex (you need to handle callbacks from Google), but it does give you critical information to work with when calculating shipping.
hth....
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I currently work in a small business (15-20 employees, 5 programmers) where most projects are custom built CMS and a few web applications products.
Since I started working there, I have worked on many projects, but specifications for each project vary a lot. Sometimes we get a little detail, a Word document telling what the client wants, and what we are suggesting (suggested form fields, a short description of display, etc.). Sometimes almost nothing except "do what you think is the best approach for this project/module/request".
My question to you guys, who might work in different kind of businesses, is: How (huge pile of paper? Word docs? Visios?) and what kind of information do you get from your superiors, managers, teamates when starting a project (plenty of analysis, drawings, etc.)? How much detail do you get on this?
Hope my question is clear enough, thank you.
Specs..that's kind of funny...how about never :(.
Seriously a lot of companies assume specs aren't needed, its absolutely unacceptable but this is how it is in a LOT of companies. They assume a one liner and the programmer knows what the program should do, the inputs / outputs and so on.
Unfortunately in my case I have to actually help write the specs..and Im the programmer :(.
I mostly get a lot of verbal direction and I use a voice recorder to record the conversation and transcribe it when I am done. I write my own specs from my customers' words.
Then, as a good consultant should, I take the writeup back to the customer and verify it, and get a signature and build it, and they live happily every after! (no they dont, they change their mind a 100 times)
It can vary depending on what group the work falls under:
Support request - If the change will take a short period of time and is fixing something broken, there is this group. This could be as simple as, "Add Bob to the list of authorized users for that ancient form" where the form is something written years ago and aside from adding and removing users, it isn't touched for fear of breaking things.
Service Advisory Committee request - Items that are up to a few days are in this group as these are kind of like mini-projects as the request may be to create a new form or portal for a group. This could be upgrading some 3rd party software where we have some customizations that make the upgrade not necessarily a simple thing for Operations to do.
Project - In this case there are usually a few Word documents and/or e-mail threads that help nail down requirements in terms of scope, budget, and time. These can take months though there is something to be said for having a prototype to change rather than creating the initial prototype to tell if requirements are really met or not. Course my current project is over a year old, still has a few more months to the timeline and already has a successor coming after it is done,i.e. there is a Phase II to go after Phase I.
Uber project - These merit their own group of documentation and are the million dollar, multiple company projects that usually try to document everything up front rarely works out well here. Thus, there is some adoptioon of agile for these but there are still some growing pains to go through as how we use agile matures. Think installing a dozen modules of some off-the-shelf software that requires both internal and external developers to customize the suite for our specific needs as the software is supposed to be very robust, flexible and help save lots of time and money on how people otherwise do their jobs generally. Think ERP or CRM for a couple of examples here.
We are a 16-person company that creates and supports customized software for small retail shop owners.
The projects we get fall into three general categories (as related to specs):
"Here, automate this form." A sales person explains that our customer only wants this form to appear where they can fill it out and print it to make it look professional to their customer. Our specs is a single piece of paper that looks something like an order form or report. This is always false; they want pop-up lookups, automatic updating from other sources, and "while you're at it" add-ons that more than double the time. These, we've learned to just live in the moment and let the project take its course. By the time we're done, the program doesn't look anything like their original form.
Small changes. Like a simple e-mail explaining that the background color is stale, or a request to sort a report by a different column. These, we just do as time allows.
Big company integrations, where we're tasked with making our software work with some big outfit like Intuit (QuickBook) or FedEx (shipping rates). These often have well thought out documentation and sample code. We get 100's of pages in word documents or pdfs. The problem with these is when their specs are wrong. We find out about inaccuracies when we try to test or certify our integration. In these instances, we usually take longer in certification than we did to originally develop the processes.
In all cases, the real trouble is when a sales person promises a solution to the customer before even asking a programmer what it would take. As recently as 2 weeks ago, a sales person got into real trouble and had to issue a refund (that person is no longer with the company).
None - at least not from management.
Instead, as a developer (and particularly one leading a software project right now), I'm expected to contact my users/customers/etc and work directly with them to come up with our specifications and requirements. The documentation I do request from my team is only what will be useful to the team. I am lucky in that management rarely requests a document that doesn't make sense or won't provide some use to our project.
I currently have a half-dozen or so specs each 60-80 pages. One of them is 80 pages with no table of contents. Good times.
Our Product Managers and senior engineers prepare three planning docs for our data management software projects.
High-level requirements: 1-to-3 sentence descriptions of hardware/software supported or specific feature for this project. (10-15 pages of Excel-like grids)
Technical details: Engineering implementation of each high-level requirements. Up to a page for each, depending on amount of detail. (30-40 pages of filled-in feature details)
Business agreement: Summary of 1 & 2 with engineering schedule and Product Mgmt's market analysis. Everyone signs off on this. (5 pages analysis, 20 technical)
I haven't seen work flows or other Visio-like details in our specs. The prioritized requirements and schedule prove critical, so we understand when to lop things off to save development and testing time.