Barış Güler
2023
Tech Vision
More than 15 years of active development and management roles in different industries like e-commerce, travel, telecommunications and food delivery. Previously worked at Intel, Blacklane and currently at Delivery Hero.
Thinks that post-agile methods will be the next step of the today's software solution building processes.
Interested in a possibility of an egalitarian world of people supporting each other by helping to solve the problems of current world & believes the knowledge is powerful once it is shared.
Background
Vision for Tech
What tech trends should a tech company invest in for the next 1 to 2 years?
Technology is a useful servant but a dangerous master.
– Christian Lous Lange
WebAssembly
- Faster, more secure
- More portable
- Smaller than containers
- Cloud-native nature
- Runs well w/ Docker & K8
- Plays well w/ Serverless
- Increasing community support
- ByteCode Alliance
- CNCF
Binaries w/ less footprint
Edge Computing
Distribute Closer to customers
- Plays well w/ mobile-postmodern world
- Scales well w/ Distribution, Execution, Persistance & IoT
- Runs well w/ Serverless
- Plays well w/ CRDTs
- Already adopted by several companies like AWS, GCP, Cloudflare, Fastly, etc.
Infrastructure as Code (IaC)
Cloud is multiplexed today
- Runs well for Reproducible Environments
- Reduced time for computing ceremonies
- Support for Cross-cloud
- Better switch in between providers w/o vendor-lock
- Single place for different aspects: Development, Infrastructure, Security, IAM & Operations
Multi-Model Persistance
Today's data is more unstructured than we think
- Integrates well w/ multiple sources / providers
- Supports horizontal scaling
- Resilliency w/ Flexibility
- Performant
- More productivity
- Less cost of maintenance
- Industry-proven
AI/ML at Edge
Intelligency comes to IoT
- Answers well to demands for less energy consuming
- Faster than cloud
- Costs less than "cloud-only" approaches
- Plays well w/ singularity & authenticity for security
- Increasing community interest
Event-driven Microservices
Software-as-Events (SaE)
- Answers well to today's consumer-based demand culture
- Better Individualised Scalability
- Plays well w/ Edge-native environments
- Events as actionable commands to systems
- Plays well w/ transactional systems
- Possibility for Standardisation
Serverless (aka. Function Farms)
Servers still exist, btw :)
- Easier for scalability
- Answers well to high demand
- Faster deployments
- Flexible by nature
- Plays well w/ Event-driven Architectures (EDA)
- Less cost for resources
- Plays nice for PoCs / MVPs
- Replacement for BFFs
- Greener technology
Buildless Web
Future w/o Webpack
- Plays well w/o huge bundles
- No transpilation and|or builds = less time
- Web-native approach
- Support for ESM by browsers
- Easier to switch in between environments
- Examples are in rise: Deno etc.
PWAs
Reach out w/o installing an app
- Plays well w/ different paradigms: Web, Mobile, Desktop, even for IoT.
- Easy deployments
- Less costs
- Supports development by smaller teams
- No device silos
- Faster w/o approval processes by providers
- Fully Web-native
- Better performance gains
- High a11y results
Documentation as Code
Document as you code
- Better collaboration w/ domain experts
- Implements accuracy w/o outdated information
- Versional documentations
- Easy to be automated
Synthetic Data
- Plays well w/ cases if there are less real data.
- Works well w/ generating test cases for real scenarios.
- Can replace sensitive data w/ the synthetic one.
Thank You!
Questions?
Experience for Tech
What personal learnings from you tech experience would I bring?
What new technology does is create new opportunities to do a job that customers want done.
– Tim O’Reilly
Industry Insights with Innovative Market Awareness
Generation and management of new ideas based on industry insights within the tech group of the organisation
Future-oriented Mindset
Envisioning the company’s tech guidelines for near / long future in conjunction with applicability and customer demands
Customer-Oriented Approach
Understanding of the problems from clients to provide affective / tech-proven solutions in a fast paced environment.
Strategic Thinking
Combining short-term gains with long term goals as experience across subject matter experts by multiple domains.
Company-level tech resilience plannings
Encouragement of sharing knowledge by building across different sections of the tech team(s) by letting to move as a team not as a group of individuals.
Vertical Slicing
Delivering business value for faster feedback with "The Hardest the First" mentality.
Trunk-based Development
Simpler code distribution approach for immediate result playing well with CI/CD of today with less complexity closer to production, not away.
Feature Toggling
Delivering faster with reduced risk by encouraging collaboration within tech groups than cold and risky big-bang deployments.
Evolutionary Systems Thinking
Responding well to the today's rapid changes / glitches of industries while playing perfectly fine with Agile, Microservices, Vertical Slicing, Trunk-based Development and Feature Toggling.
E2E Reliability for Systems
Applications with full functionality with a support by well-established testing and monitoring strategies from start to finish for generating happier customers.
S.M.A.R.T.* Objectives for Tech Goals
Clear guideline generation for specific use cases with realistic and relevant outcomes in a certain time bound.
* specific, measurable, achievable, relevant, and time-bound
Emergent Software Design Mindset
Encouraging learning through experimentation with confidence of iterative development and continuous feedback cycles which matches with evolutionary design principles.
Thank You!
Questions?
Extras
What I think about postmodern development strategies in a nutshell.
Postmodern Software Delivery
During the ideation phase, expect to discuss the project in depth to clearly understand the goals and requirements.
1
Vertical Slicing
Our team makes each part of the build phase seamless with regular check-ins and deliverables.
2
Trunk-based Development
It's time to take the product live - the end if the build phase but the beginning of being in market.
3
Feature Toggling
1
Encourage faster
"go-to-live" times
3
Plan through fast but small iterations & go back / fix prev. iteration glitches
5
Ship software to be shipped starting with the first iteration of an incremental change
2
Re-couple domain experts under one flag of agile development
4
Go live faster for begin ingesting feedback from customer to produce new set of "food" for next iterations
Optimistic Software Engineering
- More accuracy for industry expectations
- "Less is more" vs. "The best is better"
- "Do it first, make it better then, turn it into the best at the end."
- Incrementation over Big-Bang Releases
- Frequent feedbacks from real users
- Continuous quality mindset over idealistic way of producing computing junk piles
- "Extreme Programming" over long term development cycles
- Confidence over perfection
Evolutionary Systems
Futurice - Baris Guler - Tech Interview
By Barış Güler
