GovTech

Originally Posted by Unregistered

Again, I dont know what DCE SS does...and his team lol

s://github.com/sausheong
s://sausheong.com/

Here you go

Originally Posted by Unregistered

s://github.com/sausheong
s://sausheong.com/

Here you go

What's he's doing as a DCE(Deputy Chief Exec), and what his dear PIC is doing (totally silent)

He's definitely posting a lot as Deputy Chief Engineer

Originally Posted by Unregistered

What's he's doing as a DCE(Deputy Chief Exec), and what his dear PIC is doing (totally silent)

He's definitely posting a lot as Deputy Chief Engineer

Give the PIC some slack la. He was working in private sector all this time and needs to adjust to quirks in working in public service. e.g. no profit/loss, nebulous KPIs, incompetent people above him who never wrong because they shirk away from making meaningful decisions (不做不错).

DCE seems to be going around picking a new team by going to hackathons and working with promising people. If he didn't select you most likely you are the reject - i.e. can complain alot but no ideas on how to solve the problem.

haha.

Originally Posted by Unregistered

Give the PIC some slack la. He was working in private sector all this time and needs to adjust to quirks in working in public service. e.g. no profit/loss, nebulous KPIs, incompetent people above him who never wrong because they shirk away from making meaningful decisions (不做不错).

DCE seems to be going around picking a new team by going to hackathons and working with promising people. If he didn't select you most likely you are the reject - i.e. can complain alot but no ideas on how to solve the problem.

haha.

Every single action he takes will be scrutinised and gossiped upon the moment he hired an entire division of people in such a manner. OGP had the same issue with their IM8 waiver and payscale, but as long as they deliver, no one brought them up much nowadays

His approach to OGP hackathon doesnt sound like hes building a new team, but rather trying to showboat that he can do 3 team worth of technical work(instead of just mentoring 3 teams)

Originally Posted by Unregistered

s://github.com/sausheong
s://sausheong.com/

Here you go

Can any one shed some light on why techies constantly feel the need to post on blogs or substack talking about their pet projects or whatever nonsense articles that nobody reads except for their subordinates who want to carry b alls?

I can understand some other jobs need to post online constantly to generate business & obtain clients like insurance agents, property agents, lawyers, consultants.

But techies are mostly employed by companies to develop products. It's all B2B stuff.

Originally Posted by Unregistered

Can any one shed some light on why techies constantly feel the need to post on blogs or substack talking about their pet projects or whatever nonsense articles that nobody reads except for their subordinates who want to carry b alls?

I can understand some other jobs need to post online constantly to generate business & obtain clients like insurance agents, property agents, lawyers, consultants.

But techies are mostly employed by companies to develop products. It's all B2B stuff.

How do you quantify you are better than the rest of the techies when so many people had experience in the same tech?

I can guarantee that most techies dont want to do the writing, but had to do it due to circumstances.

Originally Posted by Unregistered

Can any one shed some light on why techies constantly feel the need to post on blogs or substack talking about their pet projects or whatever nonsense articles that nobody reads except for their subordinates who want to carry b alls?

I can understand some other jobs need to post online constantly to generate business & obtain clients like insurance agents, property agents, lawyers, consultants.

But techies are mostly employed by companies to develop products. It's all B2B stuff.

They are posting to impress future employers and hopefully get invited as speaker for conference.

I feel the DCE is just getting too much hate just being at a level 95% can't reach.

If you think he is showboating by carrying 3 teams simultaneously for the hackathon, why don't you try yourself doing it for 4 teams? or even come up with some next level multi disciplinary project?

As for leadership issues, as they say, the mountain can only have one tiger, and definitely it's not up to the DCE to 'step up'. If they wanted the DCE to make leadership decisions then make him the CE already. so currently what you see is the result of the BOG, and not the DCE. The CE is usually selected to be someone the BOG feels they can 'control' and someone too capable may not be ideal for them.

Govtech isn't going to turn into Big Tech simply because the mission and definitely the scale is totally different.

Originally Posted by Unregistered

Some director was heard describing DCE as "Deputy Chief Engineer", as though being an engineer is a bad thing.

The joke is on the current bunch of directors who don't have technical experience nor have much management skills, who just parachuted into position.

At least DCE has technical skills and had real non govt corporate experience.

This is the reason why the public service had to bring in people from the private sector for leadership roles. The deep-seated culture that only administrators matters and that specialists/techies cannot be good administrators is what is holding back places like Govtech.

Only way to correct this is to replace the leaders.

Originally Posted by Unregistered

This is the reason why the public service had to bring in people from the private sector for leadership roles. The deep-seated culture that only administrators matters and that specialists/techies cannot be good administrators is what is holding back places like Govtech.

Only way to correct this is to replace the leaders.

Won't happen. The CE will always be a scholar administrator. There are too many of them and not enough spots in stat boards. The rest of the 'leadership' isn't important - they are there to give some semblance of making 'collective decisions'.