Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the amp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_has_paired_endpoint was called incorrectly. Function cannot be called before services are registered. The service ID "paired_routing" is not recognized and cannot be retrieved. Please see Debugging in WordPress for more information. (This message was added in version 2.1.1.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is not currently doing any hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. The function was called too early (before the plugins_loaded action) to determine the plugin source. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function amp_is_available was called incorrectly. `amp_is_available()` (or `amp_is_request()`, formerly `is_amp_endpoint()`) was called too early and so it will not work properly. WordPress is currently doing the `plugins_loaded` hook. Calling this function before the `wp` action means it will not have access to `WP_Query` and the queried object to determine if it is an AMP response, thus neither the `amp_skip_post()` filter nor the AMP enabled toggle will be considered. It appears the plugin with slug `google-analytics-for-wordpress` is responsible; please contact the author. Please see Debugging in WordPress for more information. (This message was added in version 2.0.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gotmls domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/independ/public_html/wp-includes/functions.php on line 6170
Netizen Kritik Kod Berpakaian The Exchange 106 – Independent

Netizen Kritik Kod Berpakaian The Exchange 106

Reading Time: < 1 minute

The Exchange 106 mendapat kritikan netizen ekoran kod etika berpakaian yang dikenakan kepada penyewa atau penghuni bangunan itu, menurut laman web The Rakyat Post. Walaupun sesetengah orang telah menerima kehadirannya sejak keberadaannya, nampaknya bangunan pejabat yang mewah itu kembali menerima perhatian.

Baru-baru ini, pengurus besar Exchange 106 mengeluarkan notis untuk mengingatkan penyewa dan tetamu bahawa mereka perlu mematuhi kod pakaian perniagaan atau kasual seperti yang digariskan dalam Buku Panduan Penyewa bangunan.

Ini bermakna pakaian seperti selipar, seluar pendek dan tank top tidak dibenarkan dan dianggap tidak sesuai. Etika berpakaian adalah untuk menggambarkan The Exchange 106 sebagai bangunan Gred A Premium.

Pengumuman itu mengundang kemarahan netizen yang menganggap kod pakaian itu mengarut. Seorang netizen menyindir label “Gred A Premium” hanya dikhaskan untuk telur atau daging lembu.

Seorang lagi tertanya-tanya jika rakyat Malaysia kembali ke pemerintahan kolonial dengan kod pakaian yang ditentukan oleh orang kulit putih, manakala seorang netizen mempersoalkan jika bangunan itu akan mengusir bekas Menteri Kewangan Tun Daim Zainuddin yang kasut kegemarannya adalah selipar.

Sementara itu, beberapa orang mempertahankan kod etika berpakaian itu. Seorang netizen menegaskan bahawa kod pakaian yang sama diperkenalkan di Menara KLCC 1,2 dan 3 sejak sekian lama tanpa sebarang kekecohan. Adalah sesuatu yang masuk akal untuk mematuhi kod pakaian agar kelihatan rapi sesuai dengan suasana pekerjaan di premis perniagaan di lokasi premium. Seorang lagi netizen menulis ia agak melucukan namun jika penyewa telah tanda tangan persetujuan tanpa membaca syarat dan terma, ia adalah hak pengurus bangunan menentukan peraturan.