Mark M. Profile

EXPLORE

0.0

(0 reviews)

You're now following

Error following user.

This user does not allow users to follow them.

You are already following this user.

Your membership plan only allows 0 follows. Upgrade here.

Successfully unfollowed

Error unfollowing user.

You have successfully recommended

Error recommending user.

Something went wrong. Please refresh the page and try again.

Email successfully verified.

$50 USD / hour

basildon,

united kingdom

$50 USD / hour

It's currently 1:08 PM here

Joined April 27, 2020

0 Recommendations

Mark M.

@SilverDrifter

0.0

(0 reviews)

0.0

$50 USD / hour

basildon,

united kingdom

$50 USD / hour

N/A

Jobs Completed

N/A

On Budget

N/A

On Time

N/A

Repeat Hire Rate

Career developer with 28 years experience

Professional software developer, with 39 years’ experience in the financial sector using .Net, C#, SQL Server, etc. I have experience in developing algorithmic trading bots, not only in the financial markets but also in online sports exchanges, such as Betfair, etc.

See all .NET Developers in United Kingdom

Contact Mark M. about your job

Reviews

Changes saved

No reviews to see here!

Qualifications

Automation Anywhere

2019

This is a VERY difficult certification to pass so I'm very proud to have achieved this level of competence with AA and also, to have put it to good use having conducted several successful training session in Automation Anywhere

Automation Anywhere

2019

I have four years experience using Automation Anywhere as an RPA (Robotic Process Automation) development tool and also posess the quite unique combination of skills (AA & C#), which enable me to develop AA METABOTS

Microsoft

1994

I attained my status as a Microsoft Certified Professional in Visual Basic in the early 90's

Publications

Advanced Visual Basic 5

Microsoft Press

What, you might ask, is the Year 2000 topic doing in a Visual Basic book? Isn't the Year 2000 problem a mainframe problem for COBOL programmers to fix? I'll answer both these questions in this chapter. So even if you've never heard of the Year 2000 (frequently referred to as Y2K) issue, read on. If you've heard of it but always assumed that it wasn't a problem in Visual Basic, also read on: you might be in for a surprise.