Dan Hancok ube future plans monawada ?Salary eka wadi wenna wenna ponna gathiya diya wela yanawa kiyala hithalada pons parana thread bump kale. Maseta 1$m gattath phd 2k kalath ponnaya ponnayamai
Migrate?
Latest ads
-
Handmade Character Soft Toy Bluey Bingo- anil1961
- Updated:
-
Colombo Dahua POE Switch 8 Ports (DH-PFS3010-8ET-65)- hashaz2012
- Updated:
-
Singapore V2Ray VPN for Tunneling
- hu KANNA
- Updated:
-
Dating Website & Online Chat Room- hotvideo
- Updated:
-
DJI Mini 4 Pro Drone Combo Plus- Hawaka
- Updated:
Principal Software Engineer සහ Tech Lead අතර වෙනස?
- Thread starter Ninja_X1
- Start date
Migrate?
behavior as a professional vs behavior outside professional matters
code of ethics ugannanne mokatada ban engineering degree ekak nathi unta.
ape mason baas, helpers lath sawala nathuwa online wage wada kalanam kelinma engineer kiyala dagani
software highlevel eken design karana ekaath engineer code karana ekath engineer ewa test karana anathayoth engineer e madiwata network gagaha yana apathayoth engineer
apenam ithin baas mokaada engineer mokaada kiyala dakka gaman hoyaganna puluwanne. ubalage baas la tikai engineers la tikai computer eka issaraha monitor 2k daagana idagatta gaman wenasa hoyanna ba dennama engineer. ethics mokatada. e madiwata company walin designation ekath denawa engineer kiyala. dan eekath ara sales "executive" gaanata watila.
mageth thopi godak unge folder tika 2008 idan ekathu karala drive eke daan inne waru ganan hoyala pawle unge photo ekkama, danawanam ridila policy yannama danna puluwan. habai ithin dan ona pakak karapuwawe kiyala nikan innawa issara wage elawa elawa yanne na. nattan mamath ube level ekata watunama ubei magei wenasakuth na uba wage unta engineer nodi inna hethuwakuth nane math uba wage low level widihata hasirunama
------ Post added on Mar 30, 2021 at 6:52 PM
kawda ban "software highlevel design karana eka"
මූ හිතාගෙන ඉන්නේ CSE පොරක් ඇවිත් software එකේ "ප්ලෑන" ඇඳලා දුන්නම අනික් "බාස්"ල කොලේ තියන ඒවා keyboard එකේ type කරනවා කියල
උඹත් ඉන්නවා මැදින්
mata mehema ekak lawata wage matakai
ubata full seen eka matakada
waren software ekak tynawa high level design karanna,උඹත් ඉන්නවා මැදින්
mokada ban me kenthi gohin, ubane mewa kiyala tyne, software gana danne nattam, danna civil huththa karagrna inna one 🫣Salary eka wadi wenna wenna ponna gathiya diya wela yanawa kiyala hithalada pons parana thread bump kale. Maseta 1$m gattath phd 2k kalath ponnaya ponnayamai
waren software ekak tynawa high level design karanna,
මම මේ Engineer සර් high level design එක ඇඳලා දෙනකන් කහට කෝප්පයක් බොනවා
IESL na, mun modai, patta gobbayo kiyala mada gahala, puluwan taram pahalata dala. unta wada 5 or 6 times salary gannakota awl yana eka ahanna deyak daමම මේ Engineer සර් high level design එක ඇඳලා දෙනකන් කහට කෝප්පයක් බොනවා
thawa thread ekak giyaa munta kisima qualifications or ability ekak na one ekekta karana puluwan kiyala. itin ubalath karapanko civil wala adu kule padi ganne nathuwa 🫣
BumpIESL na, mun modai, patta gobbayo kiyala mada gahala, puluwan taram pahalata dala. unta wada 5 or 6 times salary gannakota awl yana eka ahanna deyak da
thawa thread ekak giyaa munta kisima qualifications or ability ekak na one ekekta karana puluwan kiyala. itin ubalath karapanko civil wala adu kule padi ganne nathuwa 🫣
threre are no difference between engineer n developer, but yes experience matters
IESL na, mun modai, patta gobbayo kiyala mada gahala, puluwan taram pahalata dala. unta wada 5 or 6 times salary gannakota awl yana eka ahanna deyak da
thawa thread ekak giyaa munta kisima qualifications or ability ekak na one ekekta karana puluwan kiyala. itin ubalath karapanko civil wala adu kule padi ganne nathuwa 🫣
අඩෝ උඹ US නේද ඉන්නේ? යන්න ආසාවෙන් ඉන්න කොල්ලෙක් ඉන්නවා උදව්වක් කරන්න බැරිද?
Software engineer vs dev difference
It's up to the company really, as I don't think there's a legal framework to enforce a denomination or another, or at least not that I am aware of and this might vary from country to country (for instance, the use of the term "engineer" is actually fairly regulated in France, but there are variants that are allowed for the "abusive" cases).
That being said the general trend goes like this:
It might be that some countries have a similar distinction, I just don't really know.
Back to the software engineer title... Once, one of my teacher told our class - and rightly so - that there's no such thing, as of today, as so-called "software engineering". Because engineering something (be it a building, a vehicle, a piece of hardware...) means you are capable of envisioning its design and all the phases of its production, and to predict with accuracy the resources you will need, and thus the cost of the production.
This is true of most "true" engineering disciplines. There are fluctuations, of course (the prices of the materials will vary over time, for instance), but there are very finite theoretical models (for design and planning) and empirical models (for pretty much keeping any of the former within accessible constraints) that allow you to predict the termination date of a project and its resource usage.
The major problem with software is that it is not there yet. We want to aim for software engineering, but we're not there yet, really. Because we have a very fluid and dynamic environment, very variable constraints for projects, and still a lack of maturity in retrospect in our processes. Sure we could say we get better at it (highly arguable with hard-data, though), but we've only been at it since the 60s (earlier projects were actually closer to hardware-only computers, thus closer to real engineering, ironically). Whereas we've been building motored vehicles for more than a century, vehicles in general for a few millennias, and building for even more millennias (and have been pretty damn good at it actually in some part of the world, making you feel like we're ridiculous kids playing with our new flashy software toys in comparison).
We fail to systematically predict deadlines accurately, we fail to systematically predict costs accurately, we fail to systematically identify and mitigate inherent and external risks efficiently and deterministically. The best we can manage to do is produce good enough guesstimates, and accommodate for some buffer, while trying our best to optimize the processes to reduce cycles and overhead.
But see, maybe that's what engineering is. And that's what, when someone talks about a "software engineer", they should think of and aim for.
So that seems hardly interchangeable with the simple act of programming routines, or the more advanced act of developing applications.
Still, everything is a matter of trends. Lately it's pretty common to have an horizontal dev team where everybody on the team is a Senior Software Developer (yes, capitals, because that makes us feel special, doesn't it?), without real distinction of age (fair enough, in my opinion) and not so much distinction of skills (uh-oh...) and responsibilities (now that can't be good, apart purely for PR buzz).
It's also sometimes just a force of habit and specific to an industry's culture and jargon. More positions for embedded software production use titles for software engineers. Mostly because it would probably imply that you will always have to deal to a certain extent with the hardware as well in this field, so you obviously deal with other aspects of the production and of the whole "system" you produce. Not just the bits going nuts inside it. On the other hand of the spectrum, you don't really see the term engineer being used in financial software production positions. It's either because is a mimetic evolution of this industry from one of its predecessors (say, embedded engineering find its roots in automobile engineering, for instance), or because they just want to give more or less credit/weight to a position.
And to be sure to loose everybody in the fog, you'll then find other titles mixing both (like "Software Development Engineer" or "Software Engineer in Test"!), and then other ones emphasizing even more crazy bridges with other domains (think of "Software Architect" and how "software architecture" might be a shameless theft of vocabulary). And keep them coming: Release Engineer, Change Development Manager, Build Engineer (that one goes ffaaarrrrrr out there as well). And sometimes just simply "engineer".
Hope that helped, though it's not really an answer.
Oh, and that means your new company is either trying to lure you in with a new title or that they don't really care about titles, or that you really are going to have a higher-level position. The only way of knowing is to read your job spec, talk to them and eventually give it a shot and judge for yourself. I'd hope it's the latter option and that you're happy with it (and potentially cash more in on it).
------ Post added on May 30, 2023 at 4:33 PM
It's up to the company really, as I don't think there's a legal framework to enforce a denomination or another, or at least not that I am aware of and this might vary from country to country (for instance, the use of the term "engineer" is actually fairly regulated in France, but there are variants that are allowed for the "abusive" cases).
That being said the general trend goes like this:
- A programmer position is usually the one of a professional hired to to produce the code of a computer program. It will imply that you know how to write code, can understand an algorithm and follow specifications. However, it usually stops there in terms of responsibility.
- A developer position is usually considered a super-type of the programmer position. It encompasses the same responsibilities, plus the ability to design and architect a software component, and to write the technical documentation for it (including specifications). You are able to - at least technically - lead others (so, programmers), but not necessarily a team (there comes the fuzz...)
- An engineer position would usually imply that you are a developer who has a specific type of degree, some knowledge of engineering, and is capable of designing a system (as in: a combination of software components/modules that together form a whole software entity). Basically, you see a wider picture, and you are capable of designing and explaining it and separating it into smaller modules.
It might be that some countries have a similar distinction, I just don't really know.
Back to the software engineer title... Once, one of my teacher told our class - and rightly so - that there's no such thing, as of today, as so-called "software engineering". Because engineering something (be it a building, a vehicle, a piece of hardware...) means you are capable of envisioning its design and all the phases of its production, and to predict with accuracy the resources you will need, and thus the cost of the production.
This is true of most "true" engineering disciplines. There are fluctuations, of course (the prices of the materials will vary over time, for instance), but there are very finite theoretical models (for design and planning) and empirical models (for pretty much keeping any of the former within accessible constraints) that allow you to predict the termination date of a project and its resource usage.
The major problem with software is that it is not there yet. We want to aim for software engineering, but we're not there yet, really. Because we have a very fluid and dynamic environment, very variable constraints for projects, and still a lack of maturity in retrospect in our processes. Sure we could say we get better at it (highly arguable with hard-data, though), but we've only been at it since the 60s (earlier projects were actually closer to hardware-only computers, thus closer to real engineering, ironically). Whereas we've been building motored vehicles for more than a century, vehicles in general for a few millennias, and building for even more millennias (and have been pretty damn good at it actually in some part of the world, making you feel like we're ridiculous kids playing with our new flashy software toys in comparison).
We fail to systematically predict deadlines accurately, we fail to systematically predict costs accurately, we fail to systematically identify and mitigate inherent and external risks efficiently and deterministically. The best we can manage to do is produce good enough guesstimates, and accommodate for some buffer, while trying our best to optimize the processes to reduce cycles and overhead.
But see, maybe that's what engineering is. And that's what, when someone talks about a "software engineer", they should think of and aim for.
So that seems hardly interchangeable with the simple act of programming routines, or the more advanced act of developing applications.
Still, everything is a matter of trends. Lately it's pretty common to have an horizontal dev team where everybody on the team is a Senior Software Developer (yes, capitals, because that makes us feel special, doesn't it?), without real distinction of age (fair enough, in my opinion) and not so much distinction of skills (uh-oh...) and responsibilities (now that can't be good, apart purely for PR buzz).
It's also sometimes just a force of habit and specific to an industry's culture and jargon. More positions for embedded software production use titles for software engineers. Mostly because it would probably imply that you will always have to deal to a certain extent with the hardware as well in this field, so you obviously deal with other aspects of the production and of the whole "system" you produce. Not just the bits going nuts inside it. On the other hand of the spectrum, you don't really see the term engineer being used in financial software production positions. It's either because is a mimetic evolution of this industry from one of its predecessors (say, embedded engineering find its roots in automobile engineering, for instance), or because they just want to give more or less credit/weight to a position.
And to be sure to loose everybody in the fog, you'll then find other titles mixing both (like "Software Development Engineer" or "Software Engineer in Test"!), and then other ones emphasizing even more crazy bridges with other domains (think of "Software Architect" and how "software architecture" might be a shameless theft of vocabulary). And keep them coming: Release Engineer, Change Development Manager, Build Engineer (that one goes ffaaarrrrrr out there as well). And sometimes just simply "engineer".
Hope that helped, though it's not really an answer.
Oh, and that means your new company is either trying to lure you in with a new title or that they don't really care about titles, or that you really are going to have a higher-level position. The only way of knowing is to read your job spec, talk to them and eventually give it a shot and judge for yourself. I'd hope it's the latter option and that you're happy with it (and potentially cash more in on it).
------ Post added on May 30, 2023 at 4:33 PM
Last edited:
excellent ponnayo. thota ammata hikennama ridduwa kiyala feedback enawa kiyanne harima sathutui wesige puthe
dan seethale jacket 10k adan gihilla reepan
ehehehe issara podi kale wesige puthala expose karan awama goo yanawa. dan katata hinaawak enawa uparimayen ridila neda kiyala hithala
------ Post added on May 30, 2023 at 7:19 PM
apitanm software engineer da developer da, web designer da, data entry operator da adala na,mase anthimata padiya watenawan echari 
oya lamai dan gewal walata yanna
oya lamai dan gewal walata yanna
annekaiapitanm software engineer da developer da, web designer da, data entry operator da adala na,mase anthimata padiya watenawan echari
Similar threads
