Suggestions
Jasper Houtman
Microsoft Dynamics NAV/Business Central Developer and application manager at XiTec Automatisering and dtnext
Jasper Houtman is a professional working in the field of Microsoft Dynamics NAV and Business Central development and application management at dtnext B.V., a company based in the Netherlands.12
Professional Background
Jasper specializes in:
- Creating designs and change requests for new functionality in Microsoft Dynamics NAV, Business Central, CE, and F&O1
- Front-end development for Dynamics NAV and Business Central2
- Application management
He has experience working with databases, particularly Microsoft SQL Server.1
Current Role and Company
Jasper currently holds the position of Microsoft Dynamics NAV/Business Central Developer and application manager at dtnext B.V.2 The company appears to be involved in providing IT solutions and services related to Microsoft Dynamics products.
Skills and Interests
In addition to his core expertise, Jasper has shown interest in expanding his skill set. As of June 28, 2024, he was reported to be learning:
- Python programming
- Web application development
- WordPress2
This suggests that Jasper is committed to continuous learning and staying up-to-date with various technologies in the software development field.
Online Presence
Jasper maintains a professional presence on LinkedIn, where his username is jasperhoutman.12 This platform likely serves as a means for him to network with other professionals in his field and showcase his expertise in Microsoft Dynamics and related technologies.
Highlights
Python requests, can I create a "Wheel of fortune".
Yes I can. But with a bit of cheating. Programming random rotation is hard. Where we spin the wheel and based on the initial input speed then we land on a tile based on the physics of the spin.
I am way to lazy to code al of that so we need to cheat a little bit. So as soon as we initiate the spin we are going to select a random label instead. The wheel will speed up, rotate for a bit and then slow down and land on that label.
This is a common trick used for these kind of things. Like the free daily spin in the casino in GTA 5. Where you can turn a wheel to get extra RP, in game cash, a car, clothing etc. They bothered to code in the spin duration based on the speed of your spin. I did not but the end result is the same. The outcome of your spin is determined as soon as you spin the wheel. Not by the speed of the rotation caused by your input.
The end result looks like this:
Learning Python, creating a "simple" youtube app.
Creating a Youtube viewing app is not hard. If you like approving terms and conditions on every video and having to log in everytime you load a new video.
So 25% of this project was building the app. 75% of this was forcibly ripping out the annoying terms and conditions and Cookie dependency of YouTube.
Why did we need to do that? Because I can not for the life of me get google to remember my login. And YouTube really needs Cookies, but does not implement that functionality very well outside of standard browsers. To put it simply. YouTube will not remember you without a browser. Even after authenticating. So we will just no longer be doing that.
So what do we have now? We have a search query (API call) that returns the first 10 results. Open selected video opens the video in a Web view window. We distract YouTube with the PyQT5 web engine so I do not get terms and conditions and the video plays without the need for an active YouTube login.
And the end result looks like this
