Showing posts with label WWW. Show all posts
Showing posts with label WWW. Show all posts

05 March, 2014

When Top Management Kills the Opportunity for Growth

Coda (web development software)
Coda (web development software) (Photo credit: Wikipedia)
05-Mar-2014

My very first venture out of my country of birth was a job that I stayed in for almost one and a half decade. And being employed for so long means I wasn't moving from one employer to another. That is to say I didn't have the chance, or better yet, the challenge, of job hunting.

Now that I am, I realize a few things that were taken for granted for so long.

First in the list is my resume. It took me a while to remember my education details. Mine is quite unusual, coming from a 3-year technical course all units of which are credited when a BS or Degree course is pursued afterwards. It was a problem on the date of the BS Computer Science course that took me some time to realize, until I was reconciling the dates of my previous employments before the decade and a half job.

My next difficulty was the picking of the details to be included in each level or area of responsibility. Brevity is its own merit, and a lot had to be dropped, exercising of course great care not to prune where verbosity matters. This brings me to my main point of discourse.

I took on the interest of web development, and my very first small web apps was really something so small that all that mattered to me when I developed that single page was to see if I can do it. Of course I did it, and a couple of years later on, a really big project came up in the KPI list. It was considerable, and one that took me 2 years to complete: framework, UI design and bare functionality took about 8 months of development. And some other issues took priority. When the same KPI item came up the year that followed, my boss was worried that if it wasn’t completed ASAP, it would never get done at all, and it would be against me. Actually, it can be brought up again the third year, but it would already draw the attention of the next level supervisor – and that would mean bad to me and my boss.

It was done, finally. Self-UAT was carried, and then our internal group UAT followed. A few more tweaks, and it was rolled out for public use. And the requirement was: make it run only in IE, the rest of the browsers didn’t matter. Bummer!

I asked my boss why, and the directive was actually coming from IT: they will only support IE8, at that. He was anticipating any issue that may come, and if not IE, our support guys won’t even take a look. And that directive from top management was the killer.

I don’t blame them, but I have known from my research that cross-browser functionality was the very bane of web development. And form what I read, IE, being proprietary, was THE most uncompliant. No offense meant, but just pointing out that W3C compliance-wise, IE was off the chart.

And being the maverick that I am, I tacitly injected the cross-browser functionalities in my pages, not caring whether or not one day other browsers will be allowed use in the office. For even with that directive, I have tested my codes against 6 browsers:  IE, FF, Chrome, Safari, Maxthon and Opera.

I would understand that top management have to do their job of protecting their own interest, but when it comes to our working level, the decision is ours: do we let them kill our creativity and opportunity for growth?

The choice is ours. I did not. Certainly.

Enhanced by Zemanta

12 December, 2011

ASP.NET Textbox Selectall() property



12-Dec-2011


I am currently writing a form where I needed to highlight and select all text in a textbox when it is selected (onfocus), cause that is what user will be doing: copy and paste, so that in effect requires selecting the whole text string currently in the textbox, to replace it with new value.


I got two answers from my search routing, server side, and client side, and that is coming from a single article.


Here’s how:


In Page_Load event, add below code:


myTextBox.Attributes.Add("onfocus", "this.select()")


The other way is what I tested, and it worked, so I assume above works as well:





Hoe this helps you, as it did me.


Till then. Ciao!


Reference: selectall() property in C# for textbox control



Enhanced by Zemanta

16 April, 2010

Site of the week: www.tovisitornot.com

The Facebook Man. Facebook is celebrating its ...Image via Wikipedia
Some useful sites to check out. This short article is taken from TODAY, Tech - Friday, 09-April-2010

Read on...


Site of the week: www.tovisitornot.com

Do you have an online shopping addiction you need to do something about?

Or have you been obsessively checking your ex’s blog every five minutes? Tovisitornot.com can help rescue your money, time and sanity.

This website gives you a hand in breaking online addictions by limiting you to one visit within a designated period of time (say, 60 minutes).

When you try to access the site for a second time that hour, you are taken to an intervening webpage with text persuading you not to go there.

However, if you absolutely must, you can still give in to temptation after four clicks. This simple deterrent works by creating a new link from the website’s address for you to use in place of the usual one.

To Visit Or Not also helps you kick the habit by placing a timer above the website (some sites like Facebook prevent it from working, however) as a constant reminder of how long you have been there — its way of guilt-tripping you into leaving the site and, hopefully, doing something more constructive instead.

May Chua

Blogged with the Flock Browser
Reblog this post [with Zemanta]