4 ms·
"Nearshoring" in Mexico is successful primarily (IMO) because of cultural compatibilities. Plug: my firm https://magmalabs.io https://magmalabs.io When I was C
by obiefernandez 7y ago
"Nearshoring" in Mexico is successful primarily (IMO) because of cultural compatibilities. Plug: my firm https://magmalabs.io https://magmalabs.io
When I was CTO of Andela one of my main claims to fame is pioneering the "month one" curriculum, based on principles of Applied Improv -- taking comedic improvisation education and setting it in a business context. Nigeria is definitely one of those cultures where junior people are culturally ingrained in them not to disagree with their superiors. Extremely important to break them of that practice if they're going to succeed as software consultants.
- _JC_Denton 7y agoHeads up - I am getting an invalid certificate warning in your site. iOS Safari.
- cpeterso 7y agoAnd in Firefox: "Firefox does not trust this site because it uses a certificate that is not valid for magmalabs.io. The certificate is only valid for the following names: m.magmalabs.io, www.magmalabs.io Error code: SSL_ERROR_BAD_CERT_DOMAIN https://magmalabs.io/ https://magmalabs.io/ produces the error. https://www.magmalabs.io/ https://www.magmalabs.io/ does not. https://magmalabs.io/ https://magmalabs.io/ works in Chrome. Does Chrome delay the certificate validity check until after the HTTP redirect?
- cpeterso 7y agoI filed a Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1617987 https://bugzilla.mozilla.org/show_bug.cgi?id=1617987 Chrome has a heuristic they call SSLCommonNameMismatchHandling: if Chrome tries to connect to a site like "https://example.com" https://example.com" but the returned cert is for the "www." subdomain of the same domain, Chrome will silently redirect to "https://www.example.com" https://www.example.com".