Quick tech specs
- 1 ft DVI-D Male to DVI-D Female adapter cable is the ideal solution for those tight spaces where a standard straight DVI cable will not fit
- Saves wear and tear on your equipment connector
- For use with Digital CRT displays/ Flat Panel Displays/ HDTV and Projectors
- Lifetime Tripp Lite Warranty
- For use with Single or Dual TMDS Link specified equipment
- Superior molded cables with foil/braid shielding for maximum EMI/RFI protection
- DVI cable/ DVI-D M/F cable/ DVI-D to DVI-D cable
Know your gear
Tripp Lite's 0.31 m (1-ft.) DVI-D Male to DVI-D Female adapter cable is the ideal solution for those tight spaces where a standard straight DVI cable will not fit. The adapter also saves wear and tear on your video cards connector. This cable features Gold connectors and contacts, fully molded ends, and double-shielded cable.
Tripp Lite 1ft DVI Dual Link Digital Extension Cable 45 degree Left Plug is rated 4.80 out of 5 by 4.
Rated 5 out of 5 by Collette Michaels from Has a good automated deployment process and good scalability options What is most valuable? The features I am most impressed by is the automation, and when we do the pull requests, everything gets indicated on there in terms of the deployment steps and full-on automated deployment. We have found that the standard level for DevOps in terms of automated deployment is 30 minutes. So we actually hit that in 30 minutes, which was great. What needs improvement? I would like to see an improvement in the way the product owner can review changes and so forth. But I believe there are licensing costs related to that. It would be better to keep everything simple with one standard license fee. For how long have I used the solution? We've been using Git on our premises for about eight months now. What do I think about the stability of the solution? There wasn't any instability at all because when we did our first automation deployment, we hit 100% with zero bugs introduced. That was really, really good. I just think we must get the automated testing right. We don't have that many seasoned automated tests and therefore we did all the full-on regression testing that was needed, went into production and had zero defects. What do I think about the scalability of the solution? We have about 40 to 50 users and 12 testers, and so far it has been very scalable. We plan to increase our usage in the future. How are customer service and technical support? We have monitors in place for our usual business so if anything goes down, there is an immediate response to look at that from a proactive perspective to see what is affected. In terms of from a testing perspective, through change, it is a database issue or anything like that. In terms of support, we have two sections of support. One for terms of DevOps where we have a operations person responsible for this. And when we put the software into production, we have someone on standby to ensure that everything is in perfect working condition. If you previously used a different solution, which one did you use and why did you switch? There are other options in the greater part of our environments. But since we were working on Microsoft from the start, it just was easier to continue that way. It was a new department being established and we wanted to start off that way, rather than moving from an old state to a new state. It takes longer and the change management is greater. How was the initial setup? Our technical team will be able to tell you exactly, but I believe they found some problems around the installation and so forth. I do know that it took them a while to actually get the automated deployment right before they could actually execute it. Perhaps the developers can make it easier in terms of getting readiness for automation deployment. It was quite complex and it took us about a day and a half. However, if you do a manual deployment, it doesn't take that long. What other advice do I have? My advice to others would be to implement it correctly and do whatever your unit test brings back in terms of an approach. Fix that first and then start with your coding. That is how you ensure quality. I would say that you should start afresh. Instead of trying the squad branching, do the release branching, and work from there. Don't be wary of actually starting on DevOps. Sometimes people are wary of the unknown but it adds a lot of value if you go with the CDCI approach. It is a great product and my rating is eight out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2019-09-09T00:00:00-04:00
Rated 5 out of 5 by Claudiu Milea from Useful time tacking and highly stable What is our primary use case? We are using Git for development. We are cloning the code, pushing code, and raising pull requests. We use it for the typical Git workflow for development. How has it helped my organization? The solution has improved our company because I no longer have to copy the code on my own and keep it in a safe folder. This solution is organized and it's very useful in a team. What is most valuable? The most valuable feature of Git is the ease of tracking in time what the snapshot of the code was at a particular moment. The versioning is good. What needs improvement? Git could improve the merge conflicts. In a future release, the user interface should be easier to use and more intuitive. For how long have I used the solution? I have been using Git for approximately three years. What do I think about the stability of the solution? Git is highly stable. How are customer service and support? I have not used the support from Git. Which solution did I use previously and why did I switch? I have not used a similar tool prior to Git. How was the initial setup? There is only an online deployment of Git and it belongs to Microsoft. What was our ROI? We have received a return on investment using this solution. What's my experience with pricing, setup cost, and licensing? There are some extra costs to Git, but it depends on your use case. What other advice do I have? My advice to others is Git is the industry standard for source code versioning and my recommendation for them is to learn it and use it. I rate Git a nine out of ten. Which deployment model are you using for this solution? Public Cloud Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-10-21T00:00:00-04:00
Rated 5 out of 5 by Srujan Panuganti from An excellent open source, software hosting solution that provides strong version control functionality and a user-friendly interface What is our primary use case? We use this solution to host our software, and where we need to develop new features and new functionality, we create new branch from our existing software, work on our branch, develop it, test it, validate it, and then merge it with the master or main software. What is most valuable? The best thing about this solution is that it can be learned very quickly, and used very easily. What needs improvement? We would like to see tutorials added to the product, for new users to follow so that they can optimize their use of the solution. For how long have I used the solution? We have been using this solution for more than three years. What do I think about the stability of the solution? We have found this to be a very stable solution. What do I think about the scalability of the solution? This solution is easily scalable, and can comfortably handle multiple users accessing the system at the same time. How are customer service and support? This solution provides a lot of support online, that gives quick access to fixes for the majority of issues. How was the initial setup? The initial setup of this solution is very easy and straightforward. New users download the interface, using a simple command on the command line, then begin using it. What's my experience with pricing, setup cost, and licensing? This is an open-source solution, so there are no licensing fees associated with it, and no extra, 'hidden' charges. What other advice do I have? We would recommend new users to start with the areas of this solution that have a user interface. This has a step-by step guide available that will allow them to get used to the product. I would rate this solution a 10 out of 10. Which deployment model are you using for this solution? Public Cloud Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-10-26T00:00:00-04:00
Rated 5 out of 5 by Ben Mbarek from Reliable, useful tacking, and simple implementation What is our primary use case? Git can be deployed on the cloud and on-premise. What is most valuable? The most valuable feature of Git is its ability to track updates, such as firmware documentation. Additionally, many people can make changes to code without problems. It is able to solve conflicts very easily. What needs improvement? Git can improve the size of the depository it can handle and add the capability to detect the change between common files, such as Excel and PDF documents. For how long have I used the solution? I have been using Git for approximately five years. What do I think about the stability of the solution? Git is stable. What do I think about the scalability of the solution? The scalability of Git is good. We have only developed using this solution in my company. How are customer service and support? I rate the support from Git a three out of five. How would you rate customer service and support? Neutral Which solution did I use previously and why did I switch? We use another solution prior to Git. How was the initial setup? Git is not simple to set up. What about the implementation team? We did the implementation of Git in-house. Which other solutions did I evaluate? We did not evaluate other solutions. What other advice do I have? We have one person that does the maintenance of the solution that accesses the cloud services. I rate Git a ten out of ten. Disclaimer: I am a real user, and this review is based on my own experience and opinions.
Date published: 2022-11-03T00:00:00-04:00