 | Stefan Glienke on Sometimes a race condition is… |
 | dummzeuch on Sometimes a race condition is… |
 | Peter on Sometimes a race condition is… |
 | Darian on Sometimes a race condition is… |
 | Arnaud Bouchez on delphi – Why variables a… |
Posted by jpluimers on 2017/06/09
I drafted this in 2014 and given the recent QC news:
I was quite shocked to see that the Embarcadero QC client logs in over HTTP, not over HTTPS, especially since it passes the password in plain text.
QC does this logon call to http://qc.embarcadero.com/coBugCGI.exe/soap/ICDSReportPublicInterface:
Time to cut down on my usage of QC.
–jeroen
via: QC does this logon call to http://qc.embarcadero.com/coBugCGI.exe/soap/ICDSReportPublicInterface.
Posted in Delphi, Development, QC, Security, Software Development | 3 Comments »
Posted by jpluimers on 2017/06/09
QC now forwards to QP and it is no longer possible to see your older open QC posts. Since the RAD Studio IDE still appear to report issues to QC – how can we now keep track of our submitted issues?
When will the internal error reporting in RAD Studio file reports to QP instead of QC?
[WayBack] – Lars Fosdal – Google+
in a response to
[WayBack] Quality Keeps Moving Forward – Community Blogs – Embarcadero Community
A few people wondered about my (QC) criticism and some mistakenly see this as frustration.
Not being an MVP any more allows me to continue voicing these, as I get these from fellow other Delphi developers and clients.
I’m not frustrated. I voice criticism on social media as I still deeply care about the Delphi community. They are entitled to excellent products and easily searched/obtained information, especially for less than current products as these are the ones that are still widely used and made Delphi great and Borland/Inprise/Embarcadero/Idera earn a lot of money. QC is an important part of that as it has input from a lot of knowledgeable people inside the Delphi community.
Of course I know that the Delphi team has lost a lot of valuable people and resources, their infrastructure is having difficulties (hence deleting forum posts, shutting down services and even suffer from outages every now and then for which I usually warned them shortly after they happened) and they have a truckload of things on their hands. But I hardly see them reach out to the community for any help, so there is not much I can guess on how they want to be helped.
Criticism that canalizes sentiments from parts of the community at least gives them a place to respond and help set things straight.
The reason I care about the Delphi community is that they still give me a big feeling of a kind of family helping each other.
Even being in the field for well over 20 years, I still find that there are lots of Delphi things I do not know or have forgotten. Asking around in the community in a proper way usually gets me going very quickly for the former. For the latter, I have wiert.me/category/development/software-development/delphi/ and Google Search.
I spent almost a day investigating which QC links I had already archived and which I didn’t. That’s the dedication I expect from the Delphi team as well.
BTW:
This is yet another reason to keep QC: even the Tokyo release notes refer to them: [WayBack] List of new features and customer reported issues fixed in RAD Studio 10.2 Tokyo.
–jeroen
Posted in Delphi, Development, QC, Software Development | 3 Comments »
Posted by jpluimers on 2017/06/09
When you want your Mikrotik DHCP Server handout different gateways (or DNS/WINS/NTP/.. servers and other settings), many of the answers tell you to fiddle with the DHCP networks like DHCP Server different gateways – MikroTik RouterOS [WayBack] but lack concrete examples, so here we go elaborating a lot on DHCP server with static leases – MikroTik RouterOS [WayBack]:
Posted in Internet, MikroTik, Power User, Routers | Leave a Comment »
Posted by jpluimers on 2017/06/09
The locking tab of RJ45 plugs breaks very easily. Replace it by two nylon cable ties (aka zip ties), in minutes. IMPORTANT NOTES: – This must be regarded as a temporary “Mac Gyver” solution, for home usage. – Definitely not for IT staff! (no crimper? asking for one in the budget won’t get you fired!) – Before the tab breaks, consider protecting the plug.
Source: Repair a Broken Ethernet Plug – All
via: Now that’s very cool!! – Joe C. Hecht – Google+
Posted in LifeHacker, Network-and-equipment, Power User | Leave a Comment »
